dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-8994

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Project Management, Team Collaboration, Kanban Board, Gantt Charts, Task Manager and More – WP Project Manager plugin for WordPress is vulnerable to time-based SQL Injection via the ‘completed_at_operator’ parameter in all versions up to, and including, 2.6.26 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Project Manager WordPress plugin fails to properly escape the 'completed_at_operator' parameter and lacks prepared statements in its SQL query, allowing authenticated attackers with Subscriber-level access to inject time-based SQL queries for database extraction.

MitigationUpdate the WP Project Manager plugin to version 2.6.27 or later. If unable to update, disable the plugin until a patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if WP Project Manager plugin is installed
    Navigate to WordPress admin dashboard > Plugins section and locate 'WP Project Manager' in the list of installed plugins. Note the installed version displayed beneath the plugin name.
    Affected if Plugin is installed and version is lower than 2.6.27 (compare your installed version to the affected range)
  2. Verify the plugin is active
    In the Plugins section of WordPress admin, confirm the WP Project Manager plugin shows as 'Active'. An inactive plugin would not expose the vulnerable code path.
    Affected if Plugin is active and version is lower than 2.6.27
  3. Confirm subscriber-level user accounts exist
    Navigate to WordPress admin > Users section and review user roles. Subscriber-level access is the minimum privilege required to exploit this vulnerability.
    Affected if At least one user account with Subscriber role exists and the plugin version is lower than 2.6.27
  4. Inspect access to the vulnerable feature
    The vulnerability is in the 'completed_at_operator' parameter used in project/task filtering functionality. Access the Project Manager features (such as viewing projects or filtering tasks) while logged in as a Subscriber user to confirm the parameter is reachable.
    Affected if Subscriber users can access project/task listing pages and the plugin version is lower than 2.6.27

You are affected if the WP Project Manager plugin is installed, active, and running a version lower than 2.6.27 with at least one Subscriber-level user account present in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WP Project Manager plugin to version 2.6.27 or later. If unable to update, disable the plugin until a patch is available.

Recommended fix High confidence

WP Project Manager plugin version 2.6.27 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WP Project Manager' plugin
  4. Check if an update is available (version higher than 2.6.26)
  5. If an update is available, click 'Update Now' to install the latest version
  6. After updating, verify the new version number is 2.6.27 or higher
  7. Consider clearing any caching plugins if the site uses them

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8994 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8994 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data