CVE-2025-5983: Meta Tag Manager (WordPress plugin) · Open Redirect
Affects Meta Tag Manager (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Meta Tag Manager | Affected
| Fixed in– |
AI-suggested
European organizations should immediately audit user roles and permissions within WordPress installations using the Meta Tag Manager plugin, ensuring only fully trusted users have the capability to add or modify http-equiv refresh meta tags. If possible, upgrade the Meta Tag Manager plugin to version 3.3 or later once available, as this version is expected to include proper role restrictions. In the interim, consider disabling or restricting the plugin’s meta tag editing features for lower-privileged users. Implement web application firewalls (WAF) with rules to detect and block suspicious meta tag injections or unusual redirect patterns. Regularly monitor website content for unauthorized meta tag changes and conduct periodic security reviews of user privileges. Educate site administrators about the risks of open redirects and enforce strict change management processes. Additionally, employ Content Security Policy (CSP) headers to restrict allowed redirect destinations and reduce the risk of malicious redirection. Finally, maintain up-to-date backups and incident response plans to quickly recover from any exploitation attempts.
Description
The Meta Tag Manager WordPress plugin before 3.3 does not restrict which roles can create http-equiv refresh meta tags.