CVE-2022-36418 is a medium severity (CVSS 6.5) missing authorization flaw in the HREFLANG Tags Lite WordPress plugin, versions up to and including 2.0.0. Anyone can trigger it without logging in, and Patchstack lists no official patch. Remove the plugin or replace it.
What's affected
The record lists HREFLANG Tags Lite from Vagary Digital from the first release through 2.0.0. Patchstack states that no official patch is available and that the privilege required is none, so the issue is unauthenticated. The Patchstack URL describes it as an unauthenticated plugin data reset.
The record scores it 6.5 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L. Patchstack labels its own priority High and expects mass exploitation of issues of this kind. I found no report of actual exploitation, and the record's KEV flag is false, so read that as a forecast, not an observation. The class is CWE-862 (Missing Authorization).
How to check if you're exposed
Start with an inventory. If you manage the site with WP-CLI, this lists every plugin with its version and whether an update is waiting:
wp plugin list --fields=name,status,version,update
Look for the folder hreflang-tags-by-dcgws. That folder name comes from the Patchstack entry for this issue, so confirm it matches what sits under wp-content on your site. Without WP-CLI, open the Plugins screen in the dashboard and read the version shown under the name. Every version up to and including 2.0.0 is affected, and I could not confirm any fixed version.
Check staging copies, old multisite subsites and inactive plugins too. A deactivated plugin is still on disk, and some of these bugs are reachable through files that load even when the plugin is switched off, so deactivation alone is not a fix. Delete what you do not use. Because no patched release is known, the check ends with a removal decision, not an upgrade.
What to do now
- Decide whether you need the plugin. Hreflang tags can be produced by many SEO plugins or by a few lines in a theme.
- If you can, remove the plugin and re-create the hreflang data some other way first.
- If you must keep it, put a web application firewall rule or server rule in front of its endpoints and watch for resets of its data.
- Check the plugin's page and the vendor for a newer release before you decide, since the advisory may have changed after I reviewed it.
- Take a database backup so you can restore plugin settings if they are reset.
Why it matters
The endpoint that resets the plugin's data performs no permission check at all. Any visitor can ask for the reset, and the plugin does it. The damage is bounded by what the plugin stores, which is SEO markup, so the realistic harm is lost or altered hreflang configuration and the cleanup that follows. The record rates it low integrity and low availability, with nothing on confidentiality.
The more useful lesson is about abandoned software. When a plugin has no patched release, every site that keeps it takes on the risk permanently. Removing code you can replace is the cheapest fix.
Quick check
Is there a fixed version?
Patchstack says no official patch was available. I could not confirm otherwise, so check the plugin page before relying on that.
Is disabling the plugin enough?
Deactivating removes most exposure, but deleting the plugin files is cleaner and avoids a forgotten reactivation.
Sources
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.