CVE-2026-32523
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in denishua WPJAM Basic wpjam-basic allows Using Malicious Files.This issue affects WPJAM Basic: from n/a through <= 6.9.2.
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 confidenceArbitrary file upload vulnerability in WPJAM Basic WordPress plugin allows attackers to upload malicious files (e.g., PHP shells) to the server, potentially achieving remote code execution. The vulnerability stems from insufficient file type validation and authentication checks on the upload 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 WPJAM Basic plugin is installedCheck the WordPress plugins directory at wp-content/plugins/ for a wpjam-basic folder, or look for WPJAM Basic in the WordPress admin under Plugins > Installed PluginsAffected if The WPJAM Basic plugin is present in the WordPress installation
-
Determine installed WPJAM Basic versionOpen wp-content/plugins/wpjam-basic/wpjam-basic.php and locate the Version: header comment at the top of the file, or check the plugin details in WordPress admin Plugins pageAffected if The installed version matches or falls within an affected version range (compare to any official CVE advisory for specific versions)
-
Confirm file upload module is activeCheck if the file upload functionality is enabled in WPJAM Basic settings - typically found under WPJAM > 媒体文件 (Media Files) or similar upload-related settings in the WordPress admin panelAffected if The file upload feature is enabled in WPJAM Basic configuration
-
Test upload endpoint accessibilityIf accessible, send a POST request to the WPJAM upload endpoint (commonly wp-admin/admin-ajax.php?action=wpjam-upload or similar) with a test file to see if arbitrary file types are accepted without proper validationAffected if The upload endpoint accepts files without proper authentication, content-type validation, or file extension restrictions
A WordPress site is affected if WPJAM Basic is installed with a vulnerable version, has the upload feature enabled, and the upload endpoint is accessible without proper validation controls.
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 dataUpgrade to the latest version of WPJAM Basic which should contain proper file type validation, authentication checks, and file storage restrictions. If no patch is available, disable the file upload functionality or restrict access to administrative users only until a fix is released.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32523 — 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-32523 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