CVE-2025-28948
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in codedraft Mediabay - WordPress Media Library Folders allows Reflected XSS. 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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in Mediabay WordPress Media Library Folders plugin allows attackers to craft malicious requests that result in Reflected XSS. The lack of anti-CSRF tokens on sensitive actions combined with insufficient input sanitization enables attackers to execute arbitrary JavaScript in victims' browsers.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Media Library Folders plugin is installedNavigate to WordPress admin > Plugins and look for 'Media Library Folders' by Mediabay, or inspect the file system at wp-content/plugins/ for a folder matching 'media-library-folders' or similar Mediabay media folder namingAffected if The plugin is present in the WordPress installation
-
Identify the installed plugin versionIn WordPress admin > Plugins, click on the plugin name to view details, or read the main plugin PHP file header for 'Version:' field, or check wp-content/plugins/[plugin-folder]/[main-file].phpAffected if A version number is returned that matches any vulnerable version range (if known)
-
Inspect plugin for missing WordPress noncesSearch the plugin PHP files for sensitive actions (ajax calls, form submissions, state-changing operations) and verify whether wp_verify_nonce, check_ajax_referer, or wp_nonce_field is used. Run: grep -r 'wp_verify_nonce\|check_ajax_referer\|wp_nonce' wp-content/plugins/[plugin-folder]/Affected if Sensitive actions are found without nonce verification (no nonce checks present)
-
Check for input sanitization gapsSearch plugin PHP files for user-supplied input ( $_GET, $_POST, $_REQUEST ) being output without sanitization functions like esc_html, esc_attr, sanitize_text_field. Run: grep -n '\$_GET\|\$_POST\|\$_REQUEST' wp-content/plugins/[plugin-folder]/ and trace outputsAffected if User input is reflected in output without proper escaping functions
-
Verify the attack surface is accessibleCheck if the plugin admin menus or ajax endpoints are accessible to logged-in users. Inspect the plugin for admin menu registration and ajax action handlers that process requests without CSRF protectionAffected if The vulnerable endpoints are reachable by authenticated users (any admin/editor/author)
A user is affected if the Mediabay Media Library Folders plugin is active with a vulnerable version that lacks nonce verification on sensitive actions and contains unsanitized user input reflection leading to reflected XSS.
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 dataImplement WordPress nonces (anti-CSRF tokens) on all state-changing actions and apply proper input validation with output encoding to prevent the reflected XSS.
- 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-28948 — 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-28948 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