# CVE-2025-55713: WordPress Blocksy Theme <= 2.1.6 - Cross Site Scripting (XSS) Vulnerability

> Attackers can inject malicious scripts into the Blocksy WordPress theme, potentially stealing user data or hijacking sessions.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Aug 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-g4xx-hrw7-ww9q

## What is CVE-2025-55713?

CVE-2025-55713 is a medium-severity cross-site scripting vulnerability in creativethemeshq Blocksy, published on 14 Aug 2025. An attacker needs administrator access to exploit it, 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 creativethemeshq Blocksy blocksy allows Stored XSS.This issue affects Blocksy: from n/a through <= 2.1.6.

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

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


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

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

## Is CVE-2025-55713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-55713 is a medium-severity cross-site scripting vulnerability in creativethemeshq Blocksy, published on 14 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-55713 in the wild and no public exploit code.

Affected product: creativethemeshq Blocksy. 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-55713/ (Markdown: https://insights.sbomify.com/CVE-2025-55713/index.md)
```

## Sources

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

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