CVE-2022-1112: The Autolinks WordPress plugin through 1.0.1 does not have CSRF check in place when updating its settings, and

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

autolinks: upgrade to newer than 1.0.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-1112 being exploited?

CVE-2022-1112 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-1112 affect?

CVE-2022-1112 affects autolinks. Severity is medium (CVSS 5.4). The Autolinks WordPress plugin through 1.0.1 does not have CSRF check in place when updating its settings, and does not sanitise as well as escape them, which could allow attackers to perform Stored Cross-Site scripting against a logged in

Q: How urgent is CVE-2022-1112?

Priority 30/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

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

The Autolinks WordPress plugin through 1.0.1 does not have CSRF check in place when updating its settings, and does not sanitise as well as escape them, which could allow attackers to perform Stored Cross-Site scripting against a logged in admin via a CSRF attack

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 76%)
CISA exploited list	No
Weakness	CWE-79, CWE-352
Published	2022-04-18
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: autolinks project

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

Am I affected?

Timeline

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

autolinks project autolinks UPGRADE

Affected: <= 1.0.1

Fixed in: newer than 1.0.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy autolinks || rpm -q autolinks || autolinks --version

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

sudo apt update && sudo apt install --only-upgrade autolinks

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade autolinks

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-1112?

autolinks: upgrade to newer than 1.0.1. Exact commands for each OS are on this page.

Is CVE-2022-1112 being exploited?

CVE-2022-1112 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-1112 affect?

CVE-2022-1112 affects autolinks. Severity is medium (CVSS 5.4). The Autolinks WordPress plugin through 1.0.1 does not have CSRF check in place when updating its settings, and does not sanitise as well as escape them, which could allow attackers to perform Stored Cross-Site scripting against a logged in

How urgent is CVE-2022-1112?

Priority 30/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs