CVE-2022-2600
Auto-hyperlink URLs <= 5.4.1 - Tab Nabbing
No known exploitation. EPSS puts it in the 49th percentile. No fix published yet.
What to do
No fixed build or workaround is published yet. Limit exposure and watch for a patch.
- Unknown Auto-hyperlink URLsAffected: ≥ 5.4.1, ≤ 5.4.1Upgrade to: after 5.4.1Stated by: CVE record
- Auto-hyperlink Urls Project Auto-hyperlink UrlsAffected: ≤ 5.4.1Upgrade to: after 5.4.1Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check whether your WordPress site uses Auto-hyperlink URLs and whether its installed version is 5.4.1 or earlier.
- No fixed version has been published; check the plugin’s official update channel before upgrading.
- Until a fix is available, have your web developer add
rel="noopener noreferrer"to external links created by the plugin, or disable the plugin if that cannot be done. - Test a sample of affected links after the change to confirm they still work.
What it is
From the CVE record
The Auto-hyperlink URLs WordPress plugin through 5.4.1 does not set rel="noopener noreferer" on generated links, which can lead to Tab Nabbing by giving the target site access to the source tab through the window.opener DOM object.
In plain language
Written by AI from the recordAuto-hyperlink URLs through 5.4.1 can let a website opened from one of your pages interfere with the original browser tab, so small businesses using it should review their sites and act when an update is available.
Auto-hyperlink URLs through 5.4.1 is vulnerable to tab nabbing because generated external links omit `rel="noopener noreferrer"`, leaving `window.opener` available to the destination site.
If you're affected
- Misleading browser redirects
- Customer trust damage
- Phishing exposure
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.6% chance of exploitation activity in the next 30 days, which ranks it in the 49th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
4 events over 1292 days, from the signal feeds we watch.
- Nuclei check added
- Record updated
- Publishedweakness classified
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Scored 5.4 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity LowData modification is possible but limited in scope or consequence
- Availability NoneNo availability impact
Weaknesses
Sources
References in the record
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Auto-hyperlink URLs, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI