# CVE-2025-5983: Meta Tag Manager < 3.3 - Contributor+ Open Redirect

> Contributors can create http-equiv refresh meta tags, enabling open redirect attacks against users of the Meta Tag Manager WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2025
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-9x3m-44rv-9cpf

## What is CVE-2025-5983?

CVE-2025-5983 is a medium-severity vulnerability in Unknown Meta Tag Manager, published on 22 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Meta Tag Manager WordPress plugin before 3.3 does not restrict which roles can create http-equiv refresh meta tags.

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


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

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

## Is CVE-2025-5983 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5983 is a medium-severity vulnerability in Unknown Meta Tag Manager, published on 22 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5983 exists.

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

## Sources

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

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