Stored XSS via missing nonce validation
Published Oct 17, 2024 · Updated Apr 28, 2026
CSRF in RudeStan VKontakte Wall Post 2.0 and earlier allows remote attackers to store malicious scripts through a forged settings request. The settings-update path omits or incorrectly performs WordPress nonce validation, so forged values are saved; the function name is undisclosed. Exploitation requires an authenticated administrator to visit a crafted page, click a malicious link, or submit a forged form; the stored script then executes in a visitor's browser.
Summary
What happened
CSRF in RudeStan VKontakte Wall Post 2.0 and earlier allows remote attackers to store malicious scripts through a forged settings request. The settings-update path omits or incorrectly performs WordPress nonce validation, so forged values are saved; the function name is undisclosed. Exploitation requires an authenticated administrator to visit a crafted page, click a malicious link, or submit a forged form; the stored script then executes in a visitor's browser.
The record
- CVE
- CVE-2024-49313
- Published
- Oct 17, 2024
- Updated
- Apr 28, 2026
- Vendor
- RudeStan
- Product
- VKontakte Wall Post
- Classifications
- CWE-352, CAPEC-592, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 17, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo