Wp Project ManagerWordPress extension · Wedevs
CVE-2021-36826
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 · uneditedAuthenticated (subscriber or higher user role if allowed to access projects) Stored Cross-Site Scripting (XSS) vulnerability in weDevs WP Project Manager plugin <= 2.4.13 versions.
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 confidenceAuthenticated stored XSS vulnerability in weDevs WP Project Manager plugin allows users with subscriber or higher role to inject malicious JavaScript through project fields, which executes when other users view the injected content.
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.4.14CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Project Manager plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate 'WP Project Manager' by weDevs. Note whether it is installed and activated.Affected if Plugin is not installed or not activated
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find WP Project Manager, and view the version number displayed under the plugin name. Alternatively, check the version in the plugin's main file header or readme.txt.Affected if Version is below 2.4.14 (e.g., 2.4.13, 2.4.12, etc.)
-
Confirm user role access to project fieldsIn WordPress admin, go to WP Project Manager > Settings > Capabilities. Review which user roles have permission to create, edit, or view projects and their custom fields. Check if 'Subscriber' role or other low-privilege roles are granted access.Affected if Users with 'Subscriber' role or higher have access to create or edit project fields
-
Inspect project field content for malicious scriptsNavigate to WP Project Manager > Projects. Open existing projects and inspect any custom field values (such as task lists, descriptions, or metadata). View the page source or use browser developer tools to check for unsanitized HTML or JavaScript in field values.Affected if Project fields contain unsanitized user-supplied content that includes script tags or event handlers
Environment is affected if WP Project Manager plugin version is below 2.4.14 AND the plugin grants subscriber-level or higher users access to project fields where injected scripts could be stored and executed.
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.
dbcve · scoped2.4.14
Update WP Project Manager plugin to version newer than 2.4.13; until then, restrict project manager access to trusted users only or deploy WAF rules for XSS mitigation.
WP Project Manager version 2.4.14
- Backup your WordPress site before making any changes
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Find 'WP Project Manager' (weDevs) in the plugin list
- Click 'Update now' if an update is available, or manually update to version 2.4.14 or higher
- Verify the update was successful by checking the plugin version
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
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36826 — 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-2021-36826 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