dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-40773

MEDIUM · 6.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 →
71/100
Remediation priority · Elevated
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 Broken Access Control in rtMedia for WordPress, BuddyPress and bbPress <= 4.7.9 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

This is a Broken Access Control vulnerability in the rtMedia WordPress plugin affecting versions 4.7.9 and below. The issue allows subscriber-level users to access functionality or data that should be restricted to higher-privileged roles (such as administrators or moderators), likely through improper authorization checks in the plugin's code.

MitigationUpdate rtMedia to the latest version (if available) or disable the plugin until a patch is released. If the plugin is no longer maintained, replace it with an alternative media management solution.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 rtMedia plugin is installed
    Log in to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'rtMedia' in the list. Alternatively, check if the directory /wp-content/plugins/rtmedia/ exists on the server.
    Affected if The rtMedia plugin is present in the WordPress installation
  2. Determine installed rtMedia version
    In WordPress admin, click on the rtMedia plugin to view its details and note the version number. Or read the main plugin file (usually rtmedia.php) and look for the 'Version:' header in the plugin comment block.
    Affected if The installed version is 4.7.9 or any version below 4.7.9
  3. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, check if rtMedia shows as 'Active' (not 'Inactive' or 'Must-Use').
    Affected if rtMedia version 4.7.9 or below is currently active on the site
  4. Check for subscriber-level user accounts
    In WordPress admin, go to Users > All Users and review the roles column. Look for any users assigned the 'Subscriber' role.
    Affected if rtMedia 4.7.9 or below is active AND at least one Subscriber-level user account exists on the site

You are affected if rtMedia plugin version 4.7.9 or below is installed and active on your WordPress site, particularly if you have subscriber-level user accounts that could potentially access restricted administrative functions.

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 rtMedia to the latest version (if available) or disable the plugin until a patch is released. If the plugin is no longer maintained, replace it with an alternative media management solution.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

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