CVE-2026-25446
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 Upload in WishList Member X <= 3.29.0 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 · moderate confidenceA privilege escalation vulnerability in WishList Member X WordPress plugin versions 3.29.0 and below allows authenticated subscribers to upload arbitrary files to the server, potentially achieving remote code execution by placing malicious PHP files in web-accessible directories.
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.
-
Identify WishList Member X plugin installationIn WordPress admin dashboard, go to Plugins > Installed Plugins and locate 'WishList Member X' in the list. Note the version number displayed below the plugin name.Affected if The plugin is installed and the version shows 3.29.0 or lower (e.g., 3.29.0, 3.28.0, 3.27.0, etc.)
-
Verify subscriber role exists and has accessGo to WordPress dashboard > Users > Roles (or use a role management plugin) to confirm the Subscriber role is present and active in the site.Affected if The Subscriber role exists, which is required for the privilege escalation to apply since the vulnerability specifically affects authenticated subscribers.
-
Check if file upload capability is enabled for subscribersNavigate to WishList Member X settings > Membership Levels > Check the configuration for any level accessible to subscribers. Look for file upload, content upload, or attachment upload settings. Alternatively, inspect the user capabilities: create a test subscriber account and attempt to access any upload functionality in the plugin or check if the upload_files capability is assigned to the subscriber role via Users > Roles or via wp_capabilities in the wp_usermeta table.Affected if Subscribers have the ability to upload files through WishList Member X or WordPress core (upload_files capability exists for subscriber role)
You are affected if WishList Member X plugin version is 3.29.0 or below AND the Subscriber role exists with file upload capabilities enabled, allowing uploaded files to be stored in web-accessible directories.
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 WishList Member X to version 3.29.1 or later to receive the vendor patch; if immediate update is not possible, disable subscriber-level file upload capabilities or implement WAF rules to block suspicious file uploads.
- 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-2026-25446 — 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-25446 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