# CVE-2025-31468: WordPress WP_Identicon plugin <= 2.0 - Reflected Cross Site Scripting (XSS) vulnerability

> Attackers can execute arbitrary scripts in victim browsers via reflected XSS in the WP_Identicon plugin, potentially leading to session hijacking or data theft.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Apr 2025
- **Updated:** 12 May 2026
- **Also known as:** GHSA-q8ww-m84x-4x6f

## What is CVE-2025-31468?

CVE-2025-31468 is a high-severity cross-site scripting vulnerability in scottsm WP_Identicon, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in scottsm WP_Identicon wp-identicon allows Reflected XSS.This issue affects WP_Identicon: from n/a through <= 2.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-31468?


## How do I fix CVE-2025-31468?

No fix has been published for CVE-2025-31468 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-31468 being exploited?

There is no known exploitation of CVE-2025-31468 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31468 and fix it if it is affected.

What it is: CVE-2025-31468 is a high-severity cross-site scripting vulnerability in scottsm WP_Identicon, published on 3 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-31468 in the wild and no public exploit code.

Affected product: scottsm WP_Identicon. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-31468/ (Markdown: https://insights.sbomify.com/CVE-2025-31468/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-31468
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-31468
- OSV: https://osv.dev/vulnerability/CVE-2025-31468

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-31468/
Summaries are generated and may contain mistakes; the official description above is the record.