Wp Project ManagerWordPress extension · Wedevs
CVE-2023-34383
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in weDevs WP Project Manager wedevs-project-manager allows SQL Injection.This issue affects WP Project Manager: from n/a through 2.6.0.
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 confidenceSQL Injection vulnerability in the weDevs WP Project Manager WordPress plugin allows remote attackers to inject malicious SQL commands through unsanitized user input in affected parameters. The vulnerability affects versions up to and including 2.6.0, with the critical CVSS score indicating straightforward exploitation without authentication.
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
<= 2.6.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Project Manager plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Project Manager' by weDevs, or check the file system at wp-content/plugins/wp-project-manager/Affected if Plugin is present and active in the WordPress installation
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find WP Project Manager, and note the version number displayed. Alternatively, check the main plugin file header in wp-content/plugins/wp-project-manager/wp-project-manager.php for the 'Version' fieldAffected if Version is 2.6.0 or lower (any version up to and including 2.6.0)
-
Identify vulnerable code pathsExamine the plugin source code, specifically looking for AJAX handlers or REST API endpoints that handle user-supplied input and construct database queries without prepared statements. Check files in the includes/ or classes/ directories for direct $wpdb->query or $wpdb->prepare usage with unsanitized $_POST, $_GET, or $_REQUEST variablesAffected if Plugin code contains SQL queries using user input without proper sanitization or prepared statements
-
Check for signs of exploitationReview WordPress debug logs (wp-content/debug.log if debugging is enabled), server access logs, and database query logs for suspicious SQL patterns or unexpected queries targeting the plugin endpoints. Look for common SQL injection payloads or anomalous database activityAffected if Logs show SQL injection attempts or unexpected/modified database queries originating from plugin endpoints
A user is affected if the WP Project Manager plugin is installed with any version up to and including 2.6.0, as this version range contains the unsanitized SQL input vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate WP Project Manager to the latest patched version once released. Until a patch is available, review and sanitize all database queries to use prepared statements, and consider disabling the plugin if immediate risk is unacceptable.
Fix this in Wp Project Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34383 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-34383 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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