Autolinks <= 1.0.1 - Stored Cross-Site Scripting via CSRF

published 2022-04-18 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-24455

cvss: 5.4; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits: 0; none known

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

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

wpscan.com https://wpscan.com/vulnerability/746c7cf2-0902-461a-a364-285505d73505 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.4	CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	3.5	AV:N/AC:M/Au:S/C:N/I:P/A:N

Affected products

Unknown Autolinks

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation
CWE-352 Cross-Site Request Forgery

Technology feeds

WordPress rss critical rss

References

wpscan.com /vulnerability/746c7cf2-0902-461a-a364-285505d73505
exploit, third-party-advisory

Sources

CVE List CVE-2022-1112
NVD CVE-2022-1112

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary