Stored script execution via unescaped discussion subject
Published Mar 1, 2024 · Updated Mar 28, 2025
Stored XSS in PKP Open Journal Systems 3.3 allows remote attackers to execute scripts through an Add Discussion subject. The Production workflow stores the Subject value without neutralizing HTML event-handler markup before rendering it later. The public proof of concept demonstrates injection from an administrative session, and a subsequent viewer must open the discussion for script execution in that viewer’s browser.
Summary
What happened
Stored XSS in PKP Open Journal Systems 3.3 allows remote attackers to execute scripts through an Add Discussion subject. The Production workflow stores the Subject value without neutralizing HTML event-handler markup before rendering it later. The public proof of concept demonstrates injection from an administrative session, and a subsequent viewer must open the discussion for script execution in that viewer’s browser.
The record
- CVE
- CVE-2024-25436
- Published
- Mar 1, 2024
- Updated
- Mar 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 1, 2024CVE publishedPublication date reported by the CVE source.
- Mar 28, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Add Discussion subject stored-XSS proof of conceptproof of concept · demonstrated
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