CSRF in Wp-Championship Project
CVE-2022-1967
The WP Championship WordPress plugin before 9.3 is lacking CSRF checks in various places, allowing attackers to make a logged in admin perform unwanted actions, such as create and delete arbitrary teams as well as update the plugin's settings. Due to the lack of sanitisation and escaping, it could also lead to Stored Cross-Site Scripting issues
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N.
EPSS exploit prediction
EPSS: 0.005 (42.3th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 42nd percentile — 42.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.005 · newest: 0.005 · change: +0.000
Affected products
- Wp-Championship Project
- Wp Championship — versions 9.3
Weakness classification (CWE)
Public proof-of-concept exploits
References
- wpscan.com/vulnerability/02d25736-c796-49bd-b774-66e0e3fcf4c9 (Exploit, Third Party Advisory)
Frequently asked questions
- What is CVE-2022-1967?
- CVE-2022-1967 is a medium-severity vulnerability in Wp-Championship Project, classified under Cross-Site Request Forgery (CSRF). CVSS score: 6.5/10. Published 2022-07-04.
- How severe is CVE-2022-1967?
- Medium severity. CVSS v3 base score is 6.5 out of 10.
- Is CVE-2022-1967 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.