dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-39591

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Subscriber Arbitrary File Upload in WP-BusinessDirectory <= 4.0.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 · high confidence

A critical arbitrary file upload vulnerability in the WP-BusinessDirectory WordPress plugin versions 4.0.0 and below allows authenticated subscribers to upload malicious files to the server, potentially leading to remote code execution.

MitigationUpdate WP-BusinessDirectory to the latest patched version immediately. Review uploaded files and user accounts for signs of compromise.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WP-BusinessDirectory plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WP-BusinessDirectory' or 'Business Directory' in the installed plugins list
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In Plugins list, click on the plugin name to view details, or inspect the main plugin file header in wp-content/plugins/ for the 'Version' field
    Affected if The displayed version is 4.0.0 or any version below 4.0.0
  3. Verify subscriber user role exists
    Go to WordPress admin > Users and check if any users have the 'Subscriber' role assigned
    Affected if At least one user account has Subscriber role and the plugin is installed
  4. Confirm file upload functionality is accessible to subscribers
    Check the plugin settings under Business Directory > Settings or similar for upload-related options, or inspect the frontend submission form to determine if subscribers can access file upload fields
    Affected if The plugin allows file uploads and this feature is accessible to users with Subscriber role or lower privilege
  5. Inspect uploaded files directory
    Look in wp-content/uploads/ or the plugin's designated upload folder for any suspicious file types such as .php, .phtml, .exe, or scripts with double extensions
    Affected if Unexpected executable or script files are found in the upload directory

You are affected if WP-BusinessDirectory version 4.0.0 or below is installed and the file upload feature is enabled, allowing authenticated subscribers to upload files to your server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP-BusinessDirectory to the latest patched version immediately. Review uploaded files and user accounts for signs of compromise.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39591 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39591 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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