CSRF in Livesync Project
CVE-2022-1712
The LiveSync for WordPress plugin through 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
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N.
EPSS exploit prediction
EPSS: 0.004 (34.9th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 35th percentile — 34.9% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: 0.000
Affected products
- Livesync Project
- Livesync For WordPress — versions 1.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- wpscan.com/vulnerability/9ab9626f-66d5-47e4-bdb8-d8fb519f9515 (Exploit, Third Party Advisory)
Frequently asked questions
- What is CVE-2022-1712?
- CVE-2022-1712 is a medium-severity vulnerability in Livesync Project, classified under Cross-Site Request Forgery (CSRF). CVSS score: 4.3/10. Published 2022-06-08.
- How severe is CVE-2022-1712?
- Medium severity. CVSS v3 base score is 4.3 out of 10.
- Is CVE-2022-1712 known to be exploited?
- 2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.