# CVE-2025-15701: Easy Social Icons < 4.0.3 - Admin+ Stored XSS via Icon Color Settings

Status: published. Published: 2026-11-05. Updated: 2026-11-05.

The Easy Social Icons WordPress plugin before 4.0.3 does not sanitise and escape some of its settings before outputting them on front-end pages, which could allow high-privilege users such as Administrators to perform Stored Cross-Site Scripting attacks when the unfiltered_html capability is disallowed, for example on a multisite network.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / Easy Social Icons: ≥ 0; < 4.0.3 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-79

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/32a2349b-515e-4616-ab53-a7a536ade5a7/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/32a2349b-515e-4616-ab53-a7a536ade5a7/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2025-15701; retrieved 2026-11-05; source updated 2026-11-05

Revision: a719469c66037e23dbca5a0a9ac7056ec1f9e4d4276b63d25dea4de1b66c6dcd

Canonical: https://y2.dev/cve/CVE-2025-15701

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.