# CVE-2025-0522: LikeBot – Decentralized like-system <= 0.85 - Admin+ Stored XSS via CSRF

> Attackers can inject stored XSS payloads into admin sessions via CSRF, potentially leading to account takeover or code execution.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N`)
- **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:** 6 Feb 2025
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-pm4j-w673-3p6x

## What is CVE-2025-0522?

CVE-2025-0522 is a medium-severity cross-site scripting vulnerability in Unknown LikeBot, published on 6 Feb 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

The LikeBot  WordPress plugin through 0.85 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Tommietott Likebot.

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

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

## Is CVE-2025-0522 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0522 is a medium-severity cross-site scripting vulnerability in Unknown LikeBot, published on 6 Feb 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-0522 in the wild and no public exploit code.

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

## Sources

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

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