PatchTheCVECVE-2022-1826: The Cross-Linker WordPress plugin through 3.0.1.9 does not have CSRF check in place when creating Cross-Links,
CVE-2022-1826 is a medium-severity flaw (CVSS 6.5) affecting cross-linker. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The Cross-Linker WordPress plugin through 3.0.1.9 does not have CSRF check in place when creating Cross-Links, which could allow attackers to make a logged in admin perform such action via a CSRF attack
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.5% (top 55%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2022-06-20 |
| 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-1826?
cross-linker: upgrade to newer than 3.0.1.9. Exact commands for each OS are on this page.
Is CVE-2022-1826 being exploited?
CVE-2022-1826 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-1826 affect?
CVE-2022-1826 affects cross-linker. Severity is medium (CVSS 6.5). The Cross-Linker WordPress plugin through 3.0.1.9 does not have CSRF check in place when creating Cross-Links, which could allow attackers to make a logged in admin perform such action via a CSRF attack
How urgent is CVE-2022-1826?
Priority 39/100. Public exploit reference