dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-15287

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-10
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 6 weeks old

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
The rtMedia for WordPress, BuddyPress and bbPress plugin for WordPress is vulnerable to time-based SQL Injection via the order_by parameter in all versions up to, and including, 4.6.18 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

The rtMedia WordPress plugin versions up to 4.6.18 fail to properly sanitize and escape the order_by parameter before using it in a SQL query. Combined with lack of prepared statements, this allows authenticated users with subscriber-level access or higher to inject malicious SQL code, potentially extracting sensitive data from the database via time-based blind SQL injection.

MitigationUpdate to version 4.6.19 or later which contains the security patch. If unable to update immediately, consider disabling the plugin or implementing WAF rules to block malicious order_by parameter values.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate rtMedia. Note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/rtmedia/rtmedia.php for the Version field.
    Affected if The installed version is 4.6.18 or lower (any version up to and including 4.6.18 is affected).
  2. Confirm plugin is active
    In WordPress admin > Plugins, verify that rtMedia shows as 'Active' under the plugin status.
    Affected if The plugin is active and the vulnerable code is being executed.
  3. Check for existing subscriber-level or higher users
    In WordPress admin > Users, review the user list. Click on any user and check their role under 'Role' in the user profile. Subscriber, Contributor, Author, Editor, and Administrator all have subscriber-level access or higher.
    Affected if At least one user account exists with subscriber-level access or higher (roles: Subscriber, Contributor, Author, Editor, Administrator).
  4. Identify exposed order_by parameter usage
    Review your web server logs or application logs for requests to rtMedia endpoints containing the 'order_by' or 'orderby' parameter. Example: grep -r 'order_by' in wp-content/plugins/rtmedia/ to locate the vulnerable code path.
    Affected if Requests with an order_by parameter are being processed by the plugin, indicating the vulnerable code path is reachable.

You are affected if rtMedia plugin version is 4.6.18 or lower, the plugin is active, and at least one user with subscriber-level or higher access exists in WordPress.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 4.6.19 or later which contains the security patch. If unable to update immediately, consider disabling the plugin or implementing WAF rules to block malicious order_by parameter values.

Recommended fix Moderate confidence

rtMedia plugin version 4.6.19 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the rtMedia plugin
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, manually download the updated plugin from wordpress.org and upload it via Plugins > Add New > Upload Plugin
  6. Verify the updated version is 4.6.19 or higher

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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