CVE-2024-11267: The JSP Store Locator WordPress plugin through 1.0 does not sanitize and escape a parameter before using it in
CVE-2024-11267 is a high-severity flaw (CVSS 8.8) affecting jsp store locator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The JSP Store Locator WordPress plugin through 1.0 does not sanitize and escape a parameter before using it in a SQL statement, allowing user with Contributor to perform SQL injection attacks.
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.8 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.6% (top 52%) |
| CISA exploited list | No |
| Weakness | CWE-89 |
| Published | 2025-05-15 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2024-11267?
jsp store locator: upgrade to newer than 1.0. Exact commands for each OS are on this page.
Is CVE-2024-11267 being exploited?
CVE-2024-11267 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2024-11267 affect?
CVE-2024-11267 affects jsp store locator. Severity is high (CVSS 8.8). The JSP Store Locator WordPress plugin through 1.0 does not sanitize and escape a parameter before using it in a SQL statement, allowing user with Contributor to perform SQL injection attacks.
How urgent is CVE-2024-11267?
Priority 48/100. High severity; Public exploit reference
Software pages
Related CVEs
- CVE-2024-12301 MEDIUM 6.5 UPGRADE The JSP Store Locator WordPress plugin through 1.0 does not have CSRF checks in some places, which could allow