# CVE-2025-32075: IP and user agent leaks in Extension:Tabs

> Attackers can leak IP addresses and user agent strings via improper input validation in the MediaWiki Tabs Extension.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2025
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-5fq6-fcwr-3q76

## What is CVE-2025-32075?

CVE-2025-32075 is a medium-severity vulnerability in The Wikimedia Foundation Mediawiki - Tabs Extension, published on 11 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Input Validation vulnerability in The Wikimedia Foundation Mediawiki - Tabs Extension allows Code Injection.This issue affects Mediawiki - Tabs Extension: from 1.39 through 1.43.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2025-32075 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32075 is a medium-severity vulnerability in The Wikimedia Foundation Mediawiki - Tabs Extension, published on 11 Apr 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-32075 exists.

Affected product: The Wikimedia Foundation Mediawiki - Tabs Extension. 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-32075/ (Markdown: https://insights.sbomify.com/CVE-2025-32075/index.md)
```

## Sources

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

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