CVE-2026-49766
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 · uneditedSubscriber Arbitrary File Deletion in WP User Manager <= 2.9.16 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 confidenceThe WP User Manager plugin versions 2.9.16 and below contains a broken access control vulnerability allowing authenticated subscribers (the lowest privilege role) to delete arbitrary files on the server through improper authorization checks in file handling functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 User Manager plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP User Manager' in the list, or inspect the /wp-content/plugins/ directory for a folder named 'wp-user-manager'Affected if The plugin is present on the site
-
Check installed version numberIn WordPress admin, go to Plugins > Installed Plugins > WP User Manager and read the version number displayed below the plugin name, or check the version in the plugin's main PHP file headerAffected if The version is 2.9.16 or lower
-
Confirm subscriber role access existsNavigate to WordPress Users > Users panel and verify that the 'Subscriber' role exists and that users with this role can access the WordPress dashboard or frontend features provided by WP User ManagerAffected if Subscriber role users exist and can access plugin features
-
Inspect file deletion capability exposureReview the plugin's file handling or attachment deletion functionality - check if any AJAX endpoints or admin actions related to file deletion are accessible without proper capability checks (look for 'delete_file', 'remove_attachment', or similar functions in the plugin code)Affected if File deletion functionality is accessible to low-privilege authenticated users without proper authorization
If WP User Manager version 2.9.16 or lower is installed and the subscriber role can access the plugin's file deletion functionality, the environment is affected by this CVE.
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 · scopedUpgrade WP User Manager to a version higher than 2.9.16 immediately, or remove the plugin if no patched version is available.
WP User Manager 2.9.17 or latest available version
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate WP User Manager plugin
- 4. Check the current version number (ensure it is 2.9.16 or earlier)
- 5. If an update is available, click 'Update Now' to install the latest version
- 6. Alternatively, download the latest version from wordpress.org/plugins/wp-user-manager/ and upload via Plugins > Add New > Upload Plugin
- 7. Verify the updated version is installed and active
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49766 — 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-2026-49766 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