CVE-2026-39527
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 WpStream < 4.11.2 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 confidenceThe WpStream WordPress plugin before version 4.11.2 allows subscriber-level users to upload arbitrary files to the server. This improper authorization vulnerability enables authenticated users with minimal privileges to potentially upload malicious PHP scripts or other executable files, possibly leading to remote code execution.
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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 WpStream plugin is installedCheck the WordPress plugins directory or use wp-cli: wp plugin list --status=active --field=name | grep -i wpstreamAffected if WpStream plugin is present and active in the WordPress installation
-
Check WpStream plugin versionView the plugin header file (usually main plugin file) in the wpstream plugin directory or use wp-cli: wp plugin get wpstream --field=versionAffected if Installed version is earlier than 4.11.2 (for example, 4.11.1 or below)
-
Confirm subscriber role is enabledCheck WordPress user roles via wp-admin under Users > Roles, or use wp-cli: wp role list --fields=name. Also verify if user registration is allowed in Settings > General > MembershipAffected if Subscriber role exists and new user registration is enabled in the WordPress settings
-
Inspect upload directories for suspicious filesReview the wp-content/uploads/ directory (and any custom upload paths) for unexpected PHP files, scripts, or executable files that were recently uploadedAffected if Unknown PHP files or executable content is present in upload directories and the above version condition is true
You are affected if the WpStream plugin version is below 4.11.2 AND the subscriber role is accessible for user registration, allowing authenticated users with minimal privileges to potentially upload arbitrary files.
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 · scopedUpdate WpStream plugin to version 4.11.2 or later. Until then, consider restricting or disabling subscriber-level user registration and monitor for suspicious file uploads.
WpStream 4.11.2
- 1. Backup your WordPress site before making any changes
- 2. Update the WpStream plugin to version 4.11.2 or later through the WordPress admin dashboard (go to Plugins > Installed Plugins > WpStream > Update Now)
- 3. Alternatively, upload the latest version from wordpress.org via Plugins > Add New > Upload Plugin
- 4. Verify the update was successful by checking the plugin version
- 5. Test that the streaming functionality works correctly after the update
- 6. Consider reviewing user role permissions to ensure only trusted roles have upload capabilities
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39527 — 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-39527 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