Mapster WP Maps <= 2.0.5 - Unauthenticated Stored Cross-Site Scripting via 'config.loading.background' Parameter
Strategic Overview
- Status
- Patched in 2.0.6
- Affected Plugin
- Mapster WP Maps
- Affected Version
<= 2.0.5- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation
- CVE
CVE-2026-107743
At a glance
CVE-2026-107743 is a high-severity Improper Neutralization of Input During Web Page Generation vulnerability in the Mapster WP Maps WordPress plugin, affecting versions <= 2.0.5. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.6; sites on affected versions should update now. Disclosed October 2026, reported by whatm.
Vulnerability Overview
The Mapster WP Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.0.5. This is due to the /wp-json/mapster-wp-maps/save-mapmaker REST route being registered with a permission_callback that unconditionally returns true (no capability check, no nonce), together with the mapster_write_config_to_acf() helper only sanitizing string config values with sanitize_text_field() — which strips HTML tags but leaves quote characters intact — and the mapster_wp_map shortcode renderer in mapster_wordpress_maps_shortcode_display() concatenating the stored loading_background_color value into a single-quoted inline style attribute without esc_attr(). This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation
Mapster WP Maps <= 2.0.5 carries this weakness at mapster_write_config_to_acf(), and reaching it takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Mapster WP Maps the fix is 2.0.6: builds <= 2.0.5 are affected, anything from 2.0.6 onward is not.
Remediation
Update to version 2.0.6, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Mapster WP Maps 2.0.6 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
- 7.2CVE-2026-39720: Mapster WP Maps <= 2.0.4 Stored Cross-Site Scripting
CVE-2026-39720 - 6.4CVE-2025-9044: Mapster WP Maps <= 1.20.0 Stored Cross-Site Scripting
CVE-2025-9044 - 6.4CVE-2024-21744: Mapster WP Maps <= 1.2.38 Stored Cross-Site Scripting
CVE-2024-21744 - 6.1CVE-2024-13362: Freemius <= 2.10.1 Reflected DOM-Based XSS
CVE-2024-13362
Other vulnerabilities in Mapster WP Maps
- 8.8CVE-2026-12954: Mapster WP Maps <= 1.23.0 Arbitrary User Meta Write
CVE-2026-12954 - 8.8CVE-2024-9235: Mapster WP Maps Incorrect Authorization
CVE-2024-9235 - 6.4CVE-2024-10592: Mapster WP Maps <= 1.6.0 Stored Cross-Site Scripting
CVE-2024-10592 - 5.3CVE-2026-14839: Mapster WP Maps < 1.24.0 Information Exposure
CVE-2026-14839
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C