# CVE-2025-60188: WordPress Atarim plugin <= 4.2.1 - Sensitive Data Exposure vulnerability

> Attackers can retrieve embedded sensitive data from the Atarim WordPress plugin, exposing confidential information to unauthorized users.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Nov 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-648j-fchv-3hrv

## What is CVE-2025-60188?

CVE-2025-60188 is a high-severity vulnerability in Vito Peleg Atarim, published on 6 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insertion of Sensitive Information Into Sent Data vulnerability in Vito Peleg Atarim atarim-visual-collaboration allows Retrieve Embedded Sensitive Data.This issue affects Atarim: from n/a through <= 4.2.1.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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


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

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

## Is CVE-2025-60188 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60188 exists.

Public exploit code:

- CVE-2025-60188 Atarim Plugin Exploit (github_poc): https://github.com/m4sh-wacker/CVE-2025-60188-Atarim-Plugin-Exploit
- Atarim WordPress Plugin  4.2.2 - Sensitive Information Exposure (exploitdb)
- Atarim < 4.2.2 - Sensitive Information Exposure (nuclei): http/cves/2025/CVE-2025-60188.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60188 is a high-severity vulnerability in Vito Peleg Atarim, published on 6 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60188 exists.

Affected product: Vito Peleg Atarim. 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-60188/ (Markdown: https://insights.sbomify.com/CVE-2025-60188/index.md)
```

## Sources

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

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