Geomywp develops a location-based WordPress plugin available in both standard and premium versions, exposing its user base to web application vulnerabilities centered on input handling. The durable signal across its disclosures is the plugin's web interface and recurring weakness classes including improper input neutralization in SQL and cross-site scripting contexts, typical of user-facing WordPress extensions. Current exploitation activity, severity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Geomywp over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2024-6330CRITICAL The GEO my WP WordPress plugin before 4.5.0.2 does not prevent unauthenticated attackers from including arbitrary files in PHP's execution context, which leads to Remote Code Execu | Aug 19, 2024 | 9.8 | 29 | NO | NO |
CVE-2023-52134HIGH Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Eyal Fitoussi GEO my WordPress.This issue affects GEO my WordPress: from n/a t | Dec 31, 2023 | 7.2 | 21 | NO | NO |
CVE-2024-9422MEDIUM The GEO my WP WordPress plugin before 4.5, gmw-premium-settings WordPress plugin before 3.1 does not sufficiently validate files to be uploaded, which could allow attackers to uplo | Nov 22, 2024 | 6.6 | 19 | NO | NO |
CVE-2023-5467MEDIUM The GEO my WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via shortcodes in versions up to, and including, 4.0 due to insufficient input sanitization a | Oct 10, 2023 | 5.4 | 18 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Geomywp.
Media articles that mention a CVE ID that affects a product developed by Geomywp — matched by CVE ID, not by vendor name.