CVE-2022-4016 json
Booster for WooCommerce - Custom Role Creation/Deletion via CSRF
published 3y ago modified 4mo ago also EUVD-2022-51396
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
The Booster for WooCommerce WordPress plugin before 5.6.7, Booster Plus for WooCommerce WordPress plugin before 5.6.6, Booster Elite for WooCommerce WordPress plugin before 1.1.8 does not properly check for CSRF when creating and deleting Customer roles, allowing attackers to make logged admins create and delete arbitrary custom roles via CSRF attacks
Patch / fix
- Unknown Booster for WooCommerce 5.6.7
- Unknown Booster Plus for WooCommerce 5.6.6
- Unknown Booster Elite for WooCommerce 1.1.8
Is CVE-2022-4016 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/9b77044c-fd3f-4e6f-a759-dcc3082dcbd6 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
Affected products
- Unknown Booster for WooCommerce
- Unknown Booster Plus for WooCommerce
- Unknown Booster Elite for WooCommerce
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/9b77044c-fd3f-4e6f-a759-dcc3082dcbd6
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2022-4016
- NVD CVE-2022-4016
Fencer Intel 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.