dbcve.org
Wp Project ManagerWordPress extension · Wedevs

CVE-2023-49860

MEDIUM · 5.4 CVSS v3.1 Published 2023-12-14
Fix available
A fix is available. Upgrade to after 2.6.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in weDevs WP Project Manager – Task, team, and project management plugin featuring kanban board and gantt charts allows Stored XSS.This issue affects WP Project Manager – Task, team, and project management plugin featuring kanban board and gantt charts: 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 · high confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in the weDevs WP Project Manager plugin where user-supplied input is not properly sanitized before being rendered in web pages. This allows an attacker to inject malicious JavaScript code that executes in the browsers of other users viewing the affected content.

MitigationUpdate the WP Project Manager plugin to the latest version (2.6.8 or later) which should contain proper input sanitization and output escaping. If no update is available, implement output escaping at the point where user input is rendered in the application.

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

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'WP Project Manager' in the list. Note whether it appears as active or inactive.
    Affected if The plugin is installed and active in WordPress.
  2. Check the installed plugin version
    In the Plugins list, click on the plugin name or view details to find the version number displayed in the plugin metadata.
    Affected if The displayed version number is 2.6.7 or any version lower than 2.6.7.
  3. Confirm the plugin handles user-supplied input
    Navigate to a project created with WP Project Manager. Look for input fields where users can submit content such as subtasks, comments, project descriptions, or task details.
    Affected if User input fields exist and the plugin displays submitted content back to users.
  4. Test for stored XSS presence (optional verification)
    If you have a test environment, create a new task or subtask with a harmless JavaScript payload in a visible field (e.g., <img src=x onerror=alert(1)>). Save it and view the page where it displays.
    Affected if The payload renders as unescaped HTML/JavaScript rather than being displayed as plain text.

Your environment is affected if the WP Project Manager plugin version is 2.6.7 or lower and users can create or view content that includes unescaped user input.

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 a release after 2.6.7
Interim mitigation

Update the WP Project Manager plugin to the latest version (2.6.8 or later) which should contain proper input sanitization and output escaping. If no update is available, implement output escaping at the point where user input is rendered in the application.

Recommended fix Moderate confidence

Version 2.6.8 or latest available release

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find 'WP Project Manager' in the list of installed plugins
  4. 4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org
  5. 5. After updating, verify the plugin version is 2.6.8 or higher
  6. 6. Test the project management functionality to ensure the update did not break existing features
  7. 7. Clear any caching plugins or server-side caches after the update
Caveat Standard minor version updates typically do not introduce breaking changes, but test in a staging environment first if possible

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

Fix this in Wp Project Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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