dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-39503

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Unauthenticated Broken Access Control in Easy Digital Downloads <= 3.6.5 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 confidence

Unauthenticated Broken Access Control vulnerability in Easy Digital Downloads plugin versions 3.6.5 and below allows unauthenticated attackers to access functionality or data that should require proper authorization. The specific endpoints or functions affected are not detailed in available information.

MitigationUpdate Easy Digital Downloads to the latest version (greater than 3.6.5) or apply vendor-supplied security patches to remediate the broken access control. If no patch is available, consider restricting access via web server configuration or disabling affected functionality until a fix is released.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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. Verify Easy Digital Downloads plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Easy Digital Downloads' in the list, or check the filesystem at /wp-content/plugins/easy-digital-downloads/
    Affected if The plugin is not found in the WordPress installation
  2. Check the installed version of Easy Digital Downloads
    In WordPress admin, go to Plugins > Installed Plugins and click on 'View Details' for Easy Digital Downloads, or read the version from the main plugin file at /wp-content/plugins/easy-digital-downloads/easy-digital-downloads.php
    Affected if The displayed version is 3.6.5 or lower
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that Easy Digital Downloads shows as 'Active' under the plugin status
    Affected if The plugin is currently active and the version is 3.6.5 or lower
  4. Compare your version against the affected range
    Document your installed version number and compare it to the affected range: version 3.6.5 and all prior versions (e.g., 3.6.4, 3.6.3, 3.6.0, 3.5.x, etc.)
    Affected if Your installed version is 3.6.5 or any version number lower than 3.6.5

Your environment is affected if Easy Digital Downloads plugin is installed, active, and running version 3.6.5 or any earlier version, because the broken access control vulnerability impacts all those versions.

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 Easy Digital Downloads to the latest version (greater than 3.6.5) or apply vendor-supplied security patches to remediate the broken access control. If no patch is available, consider restricting access via web server configuration or disabling affected functionality until a fix is released.

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

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39503 — 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-39503 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