CVE-2026-133369 in Post Map for Google Maps Plugininfo

Summary

by MITRE • 11/21/2026

The CodePeople Post Map for Google Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'cpm_map[api_key]' parameter in all versions up to, and including, 1.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The settings form nonce is itself rendered on the Subscriber-accessible page (reachable via a trailing-slash bypass of the slug guard), making nonce verification no real barrier to the unauthorized save.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified within the CodePeople Post Map for Google Maps plugin, specifically affecting versions up through 1.3.0, represents a significant security flaw rooted in inadequate input sanitization and output escaping mechanisms. This weakness manifests as a Stored Cross-Site Scripting (XSS) vector, allowing malicious actors to inject arbitrary web scripts into pages that are subsequently executed when other users access the affected content. The core technical failure lies in how the plugin handles data passed through the cpm_map[api_key] parameter. Instead of rigorously validating and encoding this input before storage or rendering, the application accepts raw script code, which remains persistent within the database until manually removed by an administrator. This persistence distinguishes it from reflected XSS attacks, as the malicious payload is stored on the server side and served to victims upon normal page loads, thereby increasing the potential blast radius of a successful exploitation attempt.

The operational impact of this vulnerability is exacerbated by the specific access control mechanisms present in the WordPress ecosystem. While many vulnerabilities require high-level administrative privileges to exploit, this particular flaw can be leveraged by authenticated attackers possessing subscriber-level access or higher. This low privilege requirement significantly lowers the barrier for entry, as any registered user on a typical WordPress site has at least subscriber status. Furthermore, the plugin's security controls are bypassed through a trailing-slash technique that circumvents slug guards intended to restrict access to certain administrative forms. By appending a slash to the endpoint URL, attackers can reach settings pages where nonces are rendered in plain text. Although these nonces are designed to prevent Cross-Site Request Forgery by ensuring requests originate from legitimate sources, their exposure on subscriber-accessible pages effectively neutralizes this protection. Attackers can extract these nonces and use them to forge valid save requests, thereby bypassing the intended authorization checks that should have prevented unauthorized modifications to map configurations.

From a classification perspective, this vulnerability aligns with CWE-79, which describes Improper Neutralization of Input During Web Page Generation commonly known as Cross-site Scripting. The specific mechanism involves insufficient sanitization of user-supplied input before it is stored in the database and subsequent failure to escape that data during output rendering. Additionally, the ability for lower-privileged users to modify application settings via forged requests relates closely to CWE-284, Improper Access Control, as well as CWE-352, Cross-Site Request Forgery (CSRF), due to the exposure of security tokens on publicly accessible pages. In terms of offensive cybersecurity frameworks such as MITRE ATT&CK, this exploitation path corresponds to techniques involving Client-side Injection and potentially Account Manipulation if the injected scripts are used to escalate privileges or steal session cookies from other users who view the compromised map displays.

Mitigation strategies must address both the immediate technical flaws and broader security hygiene practices. The most critical step is for administrators of affected sites to upgrade the CodePeople Post Map plugin to a version later than 1.3.0, where these input validation and nonce handling issues have been resolved by the developers. Until an update can be applied, site owners should consider restricting user registration or elevating all subscriber accounts to higher privilege levels if feasible, although this may not always be practical for public-facing sites. Implementing a Web Application Firewall (WAF) with rules tuned to detect and block XSS payloads in POST requests targeting the cpm_map endpoint can provide an additional layer of defense. Furthermore, developers should ensure that any future customizations or similar plugins adhere strictly to WordPress coding standards, which mandate the use of esc_html_e for output escaping and sanitize_text_field for input sanitization. Regular security audits focusing on access control logic and nonce verification processes are essential to prevent similar trailing-slash bypasses in other components of the web application infrastructure.

Responsible

Wordfence

Reservation

11/19/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00380

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!