dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-22768

HIGH · 7.1 CVSS v3.1 Published 2025-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in JinHan Park Rocket Media Library Mime Type rocket-media-library-mime-type allows Stored XSS.This issue affects Rocket Media Library Mime Type: from n/a through <= 2.1.0.

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

A Cross-Site Request Forgery (CSRF) vulnerability in the Rocket Media Library Mime Type WordPress plugin (versions up to 2.1.0) allows attackers to craft malicious requests that result in Stored XSS. The lack of CSRF protection enables authenticated administrators to unknowingly execute attacks that inject malicious scripts into the plugin's stored data, which then executes when viewed by other users.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing actions and properly sanitize/encode all user-supplied input before storing and outputting content to prevent XSS.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Rocket Media Library Mime Type plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Rocket Media Library Mime Type' in the list of installed plugins.
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In the plugins list, click on the plugin to view its details, or check the main plugin file in wp-content/plugins/ directory for the version header in the plugin comment block.
    Affected if The version is 2.1.0 or any version lower than 2.1.0
  3. Confirm the plugin is active
    In WordPress admin, check the Plugins page to see if Rocket Media Library Mime Type has an 'Active' status under the plugin name.
    Affected if The plugin shows as Active
  4. Identify state-changing plugin features
    Access the plugin settings page (usually under Settings or Media in WordPress admin) and note any features that store user-supplied data such as mime type configurations, custom file type definitions, or media settings.
    Affected if The plugin has settings pages that accept and store user input
  5. Check for CSRF protection on plugin actions
    Inspect page source code of the plugin settings pages. Look for hidden nonce fields (wpnonce) or CSRF tokens in all forms and AJAX requests. Check the plugin PHP files for presence of wp_verify_nonce or check_admin_referer calls before any database write operations.
    Affected if No nonce fields are found in forms and no nonce verification code exists in the plugin PHP files

A user is affected if the Rocket Media Library Mime Type plugin version 2.1.0 or lower is installed and active, and the plugin lacks CSRF token verification on its configuration forms that store user input.

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

Implement anti-CSRF tokens (nonces) on all state-changing actions and properly sanitize/encode all user-supplied input before storing and outputting content to prevent XSS.

Recommended fix Moderate confidence

Upgrade to Rocket Media Library Mime Type version 2.1.1 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Rocket Media Library Mime Type' in the plugin list
  4. 4. Check if an update is available for the plugin
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. After updating, verify the plugin is running version 2.1.1 or later
  7. 7. Test that the plugin functionality remains working as expected

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

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