CVE-2022-1913: The Add Post URL WordPress plugin through 2.1.0 does not have CSRF check in place when updating its settings,
CVE-2022-1913 is a medium-severity flaw (CVSS 4.3) affecting add post url. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The Add Post URL WordPress plugin through 2.1.0 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 and lead to Stored Cross-Site Scripting 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 | 4.3 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.4% (top 63%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2022-06-27 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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-1913?
add post url: upgrade to newer than 2.1.0. Exact commands for each OS are on this page.
Is CVE-2022-1913 being exploited?
CVE-2022-1913 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-1913 affect?
CVE-2022-1913 affects add post url. Severity is medium (CVSS 4.3). The Add Post URL WordPress plugin through 2.1.0 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 and lead to Stored Cross-Site Scripting due to
How urgent is CVE-2022-1913?
Priority 29/100. Public exploit reference