Stored XSS via unvalidated settings update
Published May 15, 2025 · Updated May 20, 2025
Stored XSS in AcuGIS MapFig Studio 0.2.1 and earlier allows remote attackers to inject scripts through a forged settings request. The studio_settings handler accepts studio_apikey and studio_url values without nonce validation, sanitization, or output escaping, so crafted input is stored and rendered as script. An administrator must visit attacker-controlled content while authenticated; the stored script then executes in the WordPress administrative origin.
Summary
What happened
Stored XSS in AcuGIS MapFig Studio 0.2.1 and earlier allows remote attackers to inject scripts through a forged settings request. The studio_settings handler accepts studio_apikey and studio_url values without nonce validation, sanitization, or output escaping, so crafted input is stored and rendered as script. An administrator must visit attacker-controlled content while authenticated; the stored script then executes in the WordPress administrative origin.
The record
- CVE
- CVE-2024-6712
- Published
- May 15, 2025
- Updated
- May 20, 2025
- Vendor
- AcuGIS
- Product
- MapFig Studio
- Classifications
- CWE-352, CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2025CVE publishedPublication date reported by the CVE source.
- May 20, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.2.1
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
- WPScan forged settings request proof of conceptproof of concept · validated
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