HomeWordPress vulnerabilitiesContent Mask
Content Mask vulnerabilities
Content Mask has 3 known vulnerabilities in this database. The most recent published record is dated 9 Sep 2026.
- Known vulnerabilities
- 3
- Active installs
- 1,000+
- Latest version
- 1.8.5.6
- Last updated
- 3 Sep 2026
- Most recent
- 9 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2025-15690 | Medium 6.8 | Before 1.8.5.6 | Fixed in 1.8.5.6 | 9 Sep 2026 |
| Privilege escalation CVE-2026-77003 | Low 2.7 | Before 1.8.5.5 | Fixed in 1.8.5.5 | 23 Aug 2026 |
| Cross-site request forgery (CSRF) CVE-2022-1203 | Medium 4.3 | Before 1.8.4.1 | Fixed in 1.8.4.1 | 30 May 2022 |
Read the published descriptions
- CVE-2025-15690, 9 Sep 2026
- The Content Mask WordPress plugin before 1.8.5.6 does not properly sanitise and escape content submitted with a post before outputting it in the pages it generates, allowing users with a role as low as Contributor to perform Stored Cross-Site Scripting attacks against any user viewing or previewing the affected page. The Content Mask WordPress plugin before 1.8.5.6's option to restrict its use by role does not prevent this. CVE record
- CVE-2026-77003, 23 Aug 2026
- The Content Mask WordPress plugin before 1.8.5.5 does not check the capability required to publish the post type being created, allowing users with a role as low as Contributor to publish posts and pages on the site without holding the publish capability. CVE record
- CVE-2022-1203, 30 May 2022
- The Content Mask WordPress plugin before 1.8.4.1 does not have authorisation and CSRF checks in various AJAX actions, as well as does not validate the option to be updated to ensure it belongs to the plugin. As a result, any authenticated user, such as subscriber could modify arbitrary blog options CVE record
What to do if you run Content Mask
If you run Content Mask, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Content Mask vulnerabilities
Free. We email you when a new vulnerability is published for Content Mask, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.