CVE-2022-1759: The RB Internal Links WordPress plugin through 2.0.16 does not have CSRF check in place when updating its sett

Q: How do I fix CVE-2022-1759?

rb internal links: upgrade to newer than 2.0.16. Exact commands for each OS are on this page.

Q: Is CVE-2022-1759 being exploited?

CVE-2022-1759 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-1759 affect?

CVE-2022-1759 affects rb internal links. Severity is medium (CVSS 5.4). The RB Internal Links WordPress plugin through 2.0.16 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack, as well as perform Stored Cross-Site Sc

Q: How urgent is CVE-2022-1759?

Priority 30/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2022-1759 is a medium-severity flaw (CVSS 5.4) affecting rb internal links. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The RB Internal Links WordPress plugin through 2.0.16 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack, as well as perform Stored Cross-Site Scripting attacks due to the lack of sanitisation and escaping

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.3% (top 77%)
CISA exploited list	No
Weakness	CWE-352
Published	2022-06-13
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: rb internal links project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-06-13 13:15 UTCPublished CVE record published
2026-06-17 04:23 UTCUpdated Record last modified

rb internal links project rb internal links UPGRADE

Affected: <= 2.0.16

Fixed in: newer than 2.0.16

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy rb-internal-links || rpm -q rb-internal-links || rb-internal-links --version

2. UPGRADE to newer than 2.0.16 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade rb-internal-links

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade rb-internal-links

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-1759?

rb internal links: upgrade to newer than 2.0.16. Exact commands for each OS are on this page.

Is CVE-2022-1759 being exploited?

CVE-2022-1759 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-1759 affect?

CVE-2022-1759 affects rb internal links. Severity is medium (CVSS 5.4). The RB Internal Links WordPress plugin through 2.0.16 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack, as well as perform Stored Cross-Site Sc

How urgent is CVE-2022-1759?

Priority 30/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs