CVE-2025-28949
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Codedraft Mediabay - WordPress Media Library Folders allows Blind SQL Injection.This issue affects Mediabay - WordPress Media Library Folders: from n/a through 1.4.
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 confidenceBlind SQL injection vulnerability in Codedraft Mediabay - WordPress Media Library Folders plugin allows remote attackers to inject malicious SQL commands through unsanitized user input in the media library folders functionality, potentially enabling unauthorized database access, data exfiltration, or manipulation.
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
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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.
-
Confirm Mediabay plugin installationNavigate to WordPress admin panel > Plugins > Installed Plugins and locate 'Mediabay - WordPress Media Library Folders' or inspect the plugins directory for mediabay-related foldersAffected if The Mediabay plugin is installed and active
-
Identify installed Mediabay versionIn WordPress admin, click on the plugin to view details and note the version number, or check the plugin's main PHP file header for 'Version:' tagAffected if The installed version is lower than the patched version (specific version numbers should be obtained from the vendor advisory)
-
Verify media library folders feature is activeCheck if the Media Library Folders functionality is enabled by visiting the Media > Folders section in WordPress admin, or verify the plugin's settings/configuration for folder functionalityAffected if Media Library Folders feature is enabled and accessible to users
-
Identify vulnerable parameter entry pointsReview HTTP requests when interacting with the media folders feature (creating folders, moving media, listing folders) and identify user-supplied parameters that could be injected (such as folder names, IDs, or sorting parameters)Affected if User-controllable input is accepted by the media folders endpoints without apparent sanitization
-
Check for SQL injection indicatorsUse WordPress debug logging or a Web Application Firewall (WAF) to observe if unusual SQL syntax appears in logs, or manually test with safe SQL payloads in folder-related parameters and observe database error responsesAffected if SQL errors are returned or unexpected database queries can be triggered through folder functionality parameters
A user is affected if the Mediabay Media Library Folders plugin is installed, the media folders feature is enabled, and the installed version is lower than the vendor-patched version.
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.
From vendor dataUpdate Mediabay plugin to the latest patched version immediately; if no patched version is available, disable the plugin and implement WAF rules as a temporary compensating control.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-28949 — 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-2025-28949 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