Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NSummary
CVE-2024-10592 is a medium-severity Basic XSS (CWE-80) vulnerability in Wordpress (inferred from references). Its CVSS base score is 6.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The Mapster WP Maps plugin for WordPress is affected by a stored cross-site scripting vulnerability in all versions through 1.6.0. The flaw resides in the popup class parameter and results from insufficient input sanitization and output escaping, as indicated by its assignment to CWE-80 and a CVSS 3.1 score of 6.4.
Authenticated attackers holding contributor-level access or higher can supply malicious input that is stored and later rendered, causing arbitrary scripts to execute in the context of any user who views the affected page. The attack requires no user interaction beyond normal page access and can affect other site users due to the changed scope in the CVSS vector.
The EPSS score stands at 0.4144 with no material increase from a lower baseline after disclosure. Public references point to the plugin's WordPress directory page and a Wordfence threat intelligence entry for further details.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-33188
Vulnerability Data
The Mapster WP Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the popup class parameter in all versions up to, and including, 1.6.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated…
more
attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.1V1.3.1V1.3.3V1.3.4
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover missing or incorrect neutralization of script tags through targeted XSS test cases.
Input validation explicitly requires checking and neutralizing untrusted web inputs containing script-related characters before they reach a downstream renderer.
Secure engineering principles include mandatory output encoding and neutralization of HTML metacharacters to stop injection at the source.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require output encoding and input validation that prevent basic XSS.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches unneutralized script tags before release.
Secure SDLC mandates input validation and output encoding that directly prevent basic XSS.
Application security requirements explicitly call for neutralization of script-related HTML tags.
Secure coding standards require proper escaping of <, >, & to block XSS.
Web filtering can block some reflected XSS payloads at the network edge.