CVE-2016-10939: The xtremelocator plugin 1.5 for WordPress has SQL injection via the id parameter.
CVE-2016-10939 is a high-severity flaw (CVSS 7.2) affecting xtremelocator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The xtremelocator plugin 1.5 for WordPress has SQL injection via the id parameter.
Why this priority
- High severity
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.2 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | High |
| User interaction | None |
| EPSS exploit chance | 1.6% (top 24%) |
| CISA exploited list | No |
| Weakness | CWE-89 |
| Published | 2019-09-13 |
| 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-2016-10939?
xtremelocator: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2016-10939 being exploited?
CVE-2016-10939 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-2016-10939 affect?
CVE-2016-10939 affects xtremelocator. Severity is high (CVSS 7.2). The xtremelocator plugin 1.5 for WordPress has SQL injection via the id parameter.
How urgent is CVE-2016-10939?
Priority 49/100. High severity; Public exploit reference