Easy Google Maps < 1.14.2 - Unauthenticated Arbitrary Remote Script Inclusion
Strategic Overview
- Status
- Patched in 1.14.2
- Affected Plugin
- Easy Google Maps
- Affected Version
< 1.14.2- CVSS
- 8.1High
- Weakness type
- CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
- CVE
CVE-2026-73367
At a glance
CVE-2026-73367 is a high-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the Easy Google Maps WordPress plugin, affecting versions < 1.14.2. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.14.2; sites on affected versions should update now. Disclosed August 2026, reported by Asim Alshaya.
Vulnerability Overview
The Easy Google Maps plugin for WordPress is vulnerable to Remote File Inclusion in all versions up to 1.14.2. This is due to missing allowlist validation on the api_domain option value in the getApiDomain() function, allowing any arbitrary URL to be used as the Maps API source. This makes it possible for unauthenticated attackers to include arbitrary remote files by supplying an attacker-controlled domain as the Google Maps API domain, causing the server to load and execute scripts from an external location. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other "safe" file types can be uploaded and included.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
Easy Google Maps < 1.14.2 carries this weakness at safe, and reaching it takes no account at all. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.
Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For Easy Google Maps the fix is 1.14.2: builds < 1.14.2 are affected, anything from 1.14.2 onward is not.
Remediation
Update to version 1.14.2, 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Easy Google Maps 1.14.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Related records
Other vulnerabilities in Easy Google Maps
- 8.1CVE-2026-73366: Easy Google Maps <= 1.13.0 PHP Object Injection
CVE-2026-73366 - 6.4CVE-2024-5219: Easy Google Maps <= 1.11.15 Stored Cross-Site Scripting
CVE-2024-5219 - 6.3CVE-2025-32138: Easy Google Maps <= 1.11.18 XML Entity Injection
CVE-2025-32138 - 6.1CVE-2021-46780: Easy Google Maps <= 1.9.31 Reflected XSS
CVE-2021-46780 - 5.4CVE-2023-2526: Easy Google Maps <= 1.11.7 Cross-Site Request Forgery
CVE-2023-2526 - 5.4CVE-2023-33926: Easy Google Maps <= 1.11.7 Cross-Site Request Forgery
CVE-2023-33926 - 4.8CVE-2021-39346: Google Maps Easy <= 1.9.33 Stored Cross-Site Scripting
CVE-2021-39346 - 4.3CVE-2024-31269: Easy Google Maps <= 1.11.11 Cross-Site Request Forgery
CVE-2024-31269
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C