CVE-2021-24333 json
Content Copy Protection & Prevent Image Save <= 1.3 - CSRF to Stored Cross-Site Scripting (XSS)
published 5y ago modified 4mo ago also EUVD-2021-11246
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
The Content Copy Protection & Prevent Image Save WordPress plugin through 1.3 does not check for CSRF when saving its settings, not perform any validation and sanitisation on them, allowing attackers to make a logged in administrator set arbitrary XSS payloads in them.
Is CVE-2021-24333 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 FencerExploit prediction
0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/c722f8d0-f86b-41c2-9f1f-48e475e22864 referenced PoC, tagged "exploit" by a source, unverified
- m0ze.ru https://m0ze.ru/exploit/csrf-prevent-content-copy-image-save-v1.3.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected products
- Unknown Content Copy Protection & Prevent Image Save
Classification
- Weakness
- Technology feeds
References
-
wpscan.com
/vulnerability/c722f8d0-f86b-41c2-9f1f-48e475e22864
exploit, third-party-advisory
-
m0ze.ru
/exploit/csrf-prevent-content-copy-image-save-v1.3.html
exploit, third-party-advisory
- m0ze.ru /vulnerability/%5B2021-03-29%5D-%5BWordPress%5D-%5BCWE-352%5D-Content-Copy-Protection-Prevent-Image-Save-WordP
- m0ze.ru /vulnerability/%5B2021-03-29%5D-%5BWordPress%5D-%5BCWE-79%5D-Content-Copy-Protection-Prevent-Image-Save-WordPr
Sources
- CVE List CVE-2021-24333
- NVD CVE-2021-24333
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.