# CVE-2025-6838: Broken Link Notifier <= 1.3.0 - Authenticated (Contributor+) CSV Injection

> Authenticated attackers can inject malicious formulas into exported CSV files, leading to code execution when opened locally.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jul 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2rvj-5mf3-jpwf

## What is CVE-2025-6838?

CVE-2025-6838 is a medium-severity code injection vulnerability in apos37 Broken Link Notifier, published on 11 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Broken Link Notifier plugin for WordPress is vulnerable to CSV Injection in all versions up to, and including, 1.3.0 via broken links that are later exported. This makes it possible for authenticated attackers, with Contributor-level access and above, to embed untrusted input into exported CSV files, which can result in code execution when these files are downloaded and opened on a local system with a vulnerable configuration.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

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


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

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

## Is CVE-2025-6838 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6838 is a medium-severity code injection vulnerability in apos37 Broken Link Notifier, published on 11 Jul 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-6838 in the wild and no public exploit code.

Affected product: apos37 Broken Link Notifier. 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-6838/ (Markdown: https://insights.sbomify.com/CVE-2025-6838/index.md)
```

## Sources

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

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