XML External Entity (XXE)Weakness · CWE-611

CVE-2025-31039

CRITICAL · 9.1 CVSS v3.1 Published 2025-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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
Improper Restriction of XML External Entity Reference vulnerability in pixelgrade Category Icon category-icon allows XML Entity Linking.This issue affects Category Icon: from n/a through <= 1.0.3.

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

Improper Restriction of XML External Entity Reference (XXE) vulnerability in the pixelgrade Category Icon WordPress plugin allows remote attackers to exploit XML entity linking through malicious XML input, potentially enabling disclosure of internal files, SSRF attacks, or denial of service.

MitigationUpdate the Category Icon plugin to the latest patched version once released, or disable the plugin if no patch is available; implement XML parser hardening to disable external entity processing.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

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 Category Icon plugin is installed
    Check the WordPress plugins directory or wp-admin for the pixelgrade Category Icon plugin. Look in wp-content/plugins/ for a folder named 'category-icon' or similar.
    Affected if The plugin folder exists in the WordPress installation
  2. Determine installed plugin version
    Open the main plugin PHP file (usually category-icon.php) and locate the 'Version' header in the plugin comments, or check the readme.txt file.
    Affected if Version is at or below the unpatched release and cannot be compared to a fixed version
  3. Identify XML processing functionality
    Search plugin files for XML parsing functions (simplexml_load_file, xml_parse, SimpleXMLElement, DOMDocument::loadXML) or features that accept XML uploads/imports (import, xml, upload in function names).
    Affected if The plugin contains code that parses XML input without disabling external entity processing
  4. Confirm XML feature is accessible
    Check if the XML parsing functionality is exposed via an admin page, REST API endpoint, or front-end form. Look for admin menu entries or AJAX handlers related to category icon import/settings.
    Affected if An XML import or settings feature is available to users or unauthenticated attackers

The environment is affected if the Category Icon plugin is installed, contains vulnerable XML processing code, and the XML feature is accessible without proper XXE protections.

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 the Category Icon plugin to the latest patched version once released, or disable the plugin if no patch is available; implement XML parser hardening to disable external entity processing.

Recommended fix Moderate confidence

Latest version available from vendor (beyond 1.0.3)

  1. Check the WordPress plugin repository or contact Pixelgrade support to confirm the latest available version of the Category Icon plugin
  2. Update the Category Icon plugin to the latest version available from the WordPress plugin repository or vendor
  3. Verify the update was successful by confirming the new version number
  4. If no fixed version is available, consider temporarily disabling the Category Icon plugin until a patched version is released
  5. Review other plugins for similar XXE vulnerabilities and ensure they are also updated

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31039 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