Meta Tag Manager at a glance
- 4 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Oct 1, 2025.
- Ranked #604 by popularity on WordPress.org (70,000+ active installs).
- The latest version is 3.3 (released Sep 24, 2026). The most recent security fix shipped in 3.3.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Meta Tag Manager version
Enter the Meta Tag Manager version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Meta Tag Manager”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Meta Tag Manager”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (3.3). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Meta Tag Manager vulnerabilities
Meta Tag Manager <= 3.2 - Open Redirect
Open redirect · CVE-2025-5983
Affected versions: ≤ 3.2
Fixed in: 3.3
Severity: Medium 4.7 · Disclosed Oct 1, 2025
Meta Tag Manager <= 3.1 - Missing Authorization
Missing authorization · CVE-2025-22260
Affected versions: ≤ 3.1
Fixed in: 3.2
Severity: Medium 4.3 · Disclosed Jan 31, 2025
Meta Tag Manager <= 3.0.2 - Authenticated (Subscriber+) PHP Object Injection
PHP object injection · CVE-2024-1770
Affected versions: ≤ 3.0.2
Fixed in: 3.1
Severity: High 8.8 · Disclosed Mar 27, 2024
Freemius SDK <= 2.5.9 - Reflected Cross-Site Scripting via fs_request_get
Cross-site scripting (XSS) · CVE-2023-33999
Affected versions: ≤ 2.0.2
Fixed in: 2.1
Severity: Medium 6.1 · Disclosed Jul 18, 2023
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Meta Tag Manager <= 3.2 - Open RedirectOpen redirect · CVE-2025-5983 | ≤ 3.2 | 3.3 | Medium 4.7 | Oct 1, 2025 |
| Meta Tag Manager <= 3.1 - Missing AuthorizationMissing authorization · CVE-2025-22260 | ≤ 3.1 | 3.2 | Medium 4.3 | Jan 31, 2025 |
| Meta Tag Manager <= 3.0.2 - Authenticated (Subscriber+) PHP Object InjectionPHP object injection · CVE-2024-1770 | ≤ 3.0.2 | 3.1 | High 8.8 | Mar 27, 2024 |
| Freemius SDK <= 2.5.9 - Reflected Cross-Site Scripting via fs_request_getCross-site scripting (XSS) · CVE-2023-33999 | ≤ 2.0.2 | 2.1 | Medium 6.1 | Jul 18, 2023 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 1, 2025.
Most common weaknesses in Meta Tag Manager
Open redirect
1 issue
Links on your own domain can be used to send people to a fake site, which makes phishing emails look more convincing.
Missing authorization
1 issue
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
PHP object injection
1 issue
Specially crafted data makes the server behave in unintended ways. Combined with the right conditions, it can lead to a full takeover.
Frequently asked questions
Is Meta Tag Manager safe to use?
Meta Tag Manager is a well-known plugin with 70,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.3) and turn on automatic updates.
How do I find which version of Meta Tag Manager my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesMeta Tag Manager on WordPress.org