WordPress plugin · content-mask
Is Content Mask safe?
Safe on 1.8.5.6 or newer.
The current version, 1.8.5.6, is past every affected range on record (5 of 5 records list one). Keep it updated and you’re clear of them.
- Flaws on record
- 5
- High or critical
- 0
- Exploited
- none
- Current version
- 1.8.5.6
- Last updated
- Sep 3, 2026
- Active installs
- 1,000+
Every recorded flaw
- Sep 9, 2026Content Mask: Does not properly sanitise and escape content submitted with a post before outputting it in the pages it generatesCVE-2025-15690 · fixed in 1.8.5.6 · reported by WPScanMedium 6.8
- Aug 23, 2026Content Mask: Does not check the capability required to publish the post type being createdCVE-2026-77003 · fixed in 1.8.5.5 · reported by WPScanLow 2.7
- Sep 22, 2025Content Mask: Authorization Bypass Through User-Controlled KeyCVE-2025-58012 · affects up to 1.8.5.3 · reported by PatchstackLow 3.8
- Sep 22, 2025Content Mask: Server-Side Request Forgery (SSRF)CVE-2025-58011 · affects up to 1.8.5.2 · reported by PatchstackMedium 6.4
- May 30, 2022Content Mask: Does not have authorisation and CSRF checks in various AJAX actionsCVE-2022-1203 · fixed in 1.8.4.1 · reported by WPScan1.0% oddsMedium 4.3
Records come from the National Vulnerability Database, published by the researchers who found each flaw (Wordfence, Patchstack, WPScan and others); exploited status from CISA; exploit odds from FIRST’s EPSS; current version, installs and closures from wordpress.org, checked daily. Want every plugin on your site checked at once? Run the free website check.
Weekly security brief
The flaws that hit local websites, every Friday.
One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.