WordPress Category Icon plugin <= 1.0.3 - XML External Entity (XXE) vulnerability

published 2025-06-09 last yr. modified 2026-06-17 4mo ago also EUVD-2025-17490

cvss: 9.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits: 0; none known

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.

Is CVE-2025-31039 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: last yr. (2025-06-10)

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.1	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Affected products

pixelgrade Category Icon

Classification

Weakness

CWE-611 Improper Restriction of XML External Entity Reference

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/Wordpress/Plugin/category-icon/vulnerability/wordpress-category-icon-plugin-1-0-2-xml-external-entit
vdb-entry

Sources

CVE List CVE-2025-31039
NVD CVE-2025-31039

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.