dbcve.org
Wp Project ManagerWordPress extension · Wedevs

CVE-2023-40003

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 2.6.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Missing Authorization vulnerability in weDevs WP Project Manager wedevs-project-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Project Manager: from n/a through <= 2.6.7.

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 · moderate confidence

Missing authorization in WP Project Manager allows exploitation of incorrectly configured access control security levels, potentially enabling unauthenticated or low-privilege users to access sensitive project management functionality they should not have access to.

MitigationUpdate WP Project Manager to the latest version and audit user role and permission configurations to ensure proper access control boundaries are enforced.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Project ManagerWordPress extension
Affected:< 2.6.8

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm WP Project Manager is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Project Manager' by Wedevs in the list
    Affected if The plugin is installed and active
  2. Identify the installed version
    In the plugins list, check the version number displayed under the WP Project Manager plugin name, or check the plugin's main file header in wp-content/plugins/wppm-plugin-manager/
    Affected if Version number is less than 2.6.8
  3. Verify WordPress user role configuration
    Go to WP Project Manager > Settings > Roles and Permissions panel and inspect which user roles have access to project management features
    Affected if Unauthenticated users or low-privilege roles (like Subscriber) are granted access to sensitive project functionality
  4. Review access control settings
    Navigate to Project Manager > Settings and examine the permission settings for creating, editing, or viewing projects and tasks
    Affected if Access control settings allow users without proper authorization to access sensitive project data

Your environment is affected if WP Project Manager version is below 2.6.8 and user role/permission settings permit unauthorized access to project management functionality

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
Upgrade available Upgrade to 2.6.8 or later
Fixed in 2.6.8
Interim mitigation

Update WP Project Manager to the latest version and audit user role and permission configurations to ensure proper access control boundaries are enforced.

Recommended fix High confidence

2.6.8 or latest available version

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate WP Project Manager in the plugin list
  4. Click 'Update Now' if an update is available, or manually upload version 2.6.8 or later from the WordPress plugin repository
  5. Verify the plugin version has been updated to 2.6.8 or later
  6. Test that project management functionality continues to work correctly after the update

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

Fix this in Wp Project Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-40003 — 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-2023-40003 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