Software Issue Manager <= 5.0.0 - Unauthenticated SQL Injection
Strategic Overview
- Status
- Patched in 5.1.0
- Affected Version
<= 5.0.0- CVSS
- 7.5High
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-12877
At a glance
CVE-2026-12877 is a high-severity Improper Authentication vulnerability in the Project Management, Bug and Issue Tracking Plugin WordPress plugin, affecting versions <= 5.0.0. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 5.1.0; sites on affected versions should update now. Disclosed July 2026, reported by Mokksh Parekh.
Vulnerability Overview
The Software Issue Manager plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 5.0.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-287: Improper Authentication
Reaching this weakness in Project Management, Bug and Issue Tracking Plugin <= 5.0.0 takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For Project Management, Bug and Issue Tracking Plugin the fix is 5.1.0: builds <= 5.0.0 are affected, anything from 5.1.0 onward is not.
Remediation
Update to version 5.1.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Project Management, Bug and Issue Tracking Plugin 5.1.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Project Management, Bug and Issue Tracking Plugin – Software Issue Manager
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C