# CVE-2025-12452: Visit Counter 1.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting

> Unauthenticated attackers can trick administrators into updating settings and injecting malicious scripts via CSRF in the Visit Counter plugin.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 4 Nov 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-546r-87jx-5rwj

## What is CVE-2025-12452?

CVE-2025-12452 is a medium-severity vulnerability in bestiadurmiente Visit Counter, published on 4 Nov 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 Visit Counter plugin for WordPress is vulnerable to Cross-Site Request Forgery in version 1.0. This is due to missing or incorrect nonce validation on the widgets.php page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

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


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

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

## Is CVE-2025-12452 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-12452 is a medium-severity vulnerability in bestiadurmiente Visit Counter, published on 4 Nov 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-12452 in the wild and no public exploit code.

Affected product: bestiadurmiente Visit Counter. 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-12452/ (Markdown: https://insights.sbomify.com/CVE-2025-12452/index.md)
```

## Sources

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

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