Stored browser script execution via crafted project name
Published Jan 31, 2024 · Updated May 30, 2025
Stored XSS in POSCMS 4.6.2 allows remote authenticated users to run scripts in another user's browser through a crafted project name. The installation step stores the project-name payload without neutralization, and the home page later renders the value as executable script. Low-privileged installer access and a victim opening the home page are required; execution remains within the victim's browser context.
Summary
What happened
Stored XSS in POSCMS 4.6.2 allows remote authenticated users to run scripts in another user's browser through a crafted project name. The installation step stores the project-name payload without neutralization, and the home page later renders the value as executable script. Low-privileged installer access and a victim opening the home page are required; execution remains within the victim's browser context.
The record
- CVE
- CVE-2024-22569
- Published
- Jan 31, 2024
- Updated
- May 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 31, 2024CVE publishedPublication date reported by the CVE source.
- May 30, 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
- POSCMS 4.6.2 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