dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-1313

HIGH · 8.3 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable No privileges 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
The MimeTypes Link Icons plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.2.20. This is due to the plugin making outbound HTTP requests to user-controlled URLs without proper validation when the "Show file size" option is enabled. This makes it possible for authenticated attackers, with Contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services via crafted links in post content.

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 MimeTypes Link Icons WordPress plugin versions up to 3.2.20 are vulnerable to SSRF due to insufficient validation of user-controlled URLs when the 'Show file size' feature is enabled. Authenticated attackers with Contributor-level access can craft malicious links in post content to force the server to make arbitrary HTTP requests to internal or external resources.

MitigationUpgrade to version 3.2.21 or later, or disable the 'Show file size' option until a patch is available. Implement strict URL allowlist validation for any outbound requests.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Check if MimeTypes Link Icons plugin is installed
    Look for the mimetypes-link-icons folder in wp-content/plugins/ or find the plugin listed in WordPress admin under Plugins > Installed Plugins
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    Open the main plugin file (typically mimetypes-link-icons.php) in the plugin directory and read the Version value from the plugin header comment, or view the version in WordPress admin under Plugins
    Affected if Version is 3.2.20 or lower
  3. Verify if Show file size feature is enabled
    Access the plugin settings page in WordPress admin (usually under Settings > MimeTypes or similar) and check if the Show file size option is checked/enabled, or query the wp_options table for an option like 'mtli_show_file_size' set to 1
    Affected if The Show file size option is enabled in the plugin configuration

Environment is affected if MimeTypes Link Icons plugin version 3.2.20 or lower is installed AND the Show file size feature is currently enabled, allowing authenticated Contributor+ users to trigger SSRF via crafted links

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

Upgrade to version 3.2.21 or later, or disable the 'Show file size' option until a patch is available. Implement strict URL allowlist validation for any outbound requests.

Recommended fix High confidence

Version 3.2.21 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the MimeTypes Link Icons plugin
  4. Check if an update is available (compare current version to latest available)
  5. If update available, click 'Update Now' to upgrade to the fixed version
  6. Alternatively, manually download the fixed version from wordpress.org/plugins/mimetypes-link-icons and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the plugin is running at version 3.2.21 or higher

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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