dbcve.org
Wp Project ManagerWordPress extension · Wedevs

CVE-2024-10520

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-20
Fix available
A fix is available. Upgrade to 2.6.15 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The WP Project Manager plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check in the 'check' method of the 'Create_Milestone', 'Create_Task_List', 'Create_Task', and 'Delete_Task' classes in version 2.6.14. This makes it possible for unauthenticated attackers to create milestones, create task lists, create tasks, or delete tasks in any project. NOTE: Version 2.6.14 implemented a partial fix for this vulnerability.

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 plugin for WordPress contains a Broken Access Control vulnerability in versions up to 2.6.14. The 'check' method in multiple AJAX action classes (Create_Milestone, Create_Task_List, Create_Task, Delete_Task) lacks capability verification, allowing unauthenticated attackers to create or delete project elements via the affected endpoints.

MitigationUpdate the WP Project Manager plugin to the latest version beyond 2.6.14, as that version only provided a partial fix. Verify that unauthenticated requests to create/delete project elements are now properly rejected.

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.15

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify WP Project Manager plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Project Manager' by Wedevs. Note the installed version number displayed there.
    Affected if The plugin is installed and the version shown is below 2.6.15 (for example 2.6.14, 2.6.13, etc.)
  2. Locate plugin files for code inspection
    Access the WordPress filesystem via FTP or file manager. Navigate to /wp-content/plugins/wp-project-manager/. Identify the AJAX action class files: typically in /src/Actions/ or similar directory structure, looking for files like Create_Milestone.php, Create_Task_List.php, Create_Task.php, Delete_Task.php.
    Affected if The plugin files exist and the version is below 2.6.15
  3. Inspect the 'check' method in affected AJAX classes
    Open each of the identified AJAX action class files. Locate the 'check' or 'verify_nonce' method within each class. Examine whether the method calls current_user_can() or any capability verification function.
    Affected if The 'check' method exists but contains no capability check (current_user_can, etc.) - it likely only validates a nonce without verifying the user has permission to create/delete project elements
  4. Test AJAX endpoint accessibility without authentication
    Send a crafted POST request to /wp-admin/admin-ajax.php with action=pm_create_milestone (or similar affected action) WITHOUT providing valid authentication cookies or WordPress nonces. Use a tool like curl: curl -X POST http://target/wp-admin/admin-ajax.php -d 'action=pm_create_milestone' -d 'title=Test'
    Affected if The request is accepted and returns a successful response (not a 403 or authentication error), indicating the endpoint lacks proper access control

The environment is affected if WP Project Manager is installed with a version below 2.6.15 AND the AJAX endpoints for creating/deleting project elements are accessible to unauthenticated users without capability verification in the 'check' methods.

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.15 or later
Fixed in 2.6.15
Interim mitigation

Update the WP Project Manager plugin to the latest version beyond 2.6.14, as that version only provided a partial fix. Verify that unauthenticated requests to create/delete project elements are now properly rejected.

Recommended fix High confidence

WP Project Manager version 2.6.15

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WP Project Manager' in the plugin list
  4. If an update is available, click 'Update Now' to update to version 2.6.15 or later
  5. Alternatively, navigate to Dashboard > Updates and update the plugin from there
  6. After updating, verify the version number reflects 2.6.15 or higher in the plugins list
  7. Test that creating milestones, task lists, tasks, and delete operations work correctly for authorized users

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

Fix this in Wp Project Manager Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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