Unauthenticated script execution via unsanitized User-Agent logging
Published Feb 29, 2024 · Updated Apr 28, 2026
Stored XSS in Melapress WP Activity Log 4.6.1 and earlier allows remote attackers to execute scripts through a crafted User-Agent header. The activity-log display path stores the HTTP User-Agent value and renders it without sufficient input sanitization or output escaping. The payload runs in an administrator's browser when the injected log entry is viewed, exposing browser-accessible data and actions in that session.
Summary
What happened
Stored XSS in Melapress WP Activity Log 4.6.1 and earlier allows remote attackers to execute scripts through a crafted User-Agent header. The activity-log display path stores the HTTP User-Agent value and renders it without sufficient input sanitization or output escaping. The payload runs in an administrator's browser when the injected log entry is viewed, exposing browser-accessible data and actions in that session.
The record
- CVE
- CVE-2023-50905
- Published
- Feb 29, 2024
- Updated
- Apr 28, 2026
- Vendor
- Melapress
- Product
- WP Activity Log
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 29, 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 <=4.6.1
- Affected versionversion=n/a <=4.6.1 changes=[{"at":"4.6.2","status":"unaffected"}]
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