Content Mask 1.8.0 - 1.8.5.4 - Contributor Publish Capability Bypass via create_new_content_mask

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Unknown/Content Mask (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Unknown/Content Mask.
2. 2Review the reported fix. Update Unknown/Content Mask to 1.8.5.5 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Aug 23, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 23, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 23, 2026

Sources and claim methodology

• Source referencewpscan.com

Related CVEs

• RestrictMate < 1.3.0 - Unauthenticated Privilege Escalation to AdministratorAlso CWE-269
• Security Hardener <= 2.4.4 - Authenticated (Subscriber+) Privilege Escalation via REST API '/wp/v2/users' permission_callback OverwriteAlso CWE-269
• PPWP – Password Protect Pages <= 1.9.18 - Authenticated (Contributor+) PHP Object Injection via post_protection_rolesSame generic ecosystem
• Infineon Airoc Wi-Fi driver leaks TX buffers on send failure, leading to permanent pool exhaustionSame generic ecosystem
• WooCommerce Bookings < 3.9.0 - Subscriber+ Draft Bookable Product Creation via Missing AuthorizationSame generic ecosystem
• WebToffee WooCommerce PDF Invoices, Packing Slips, Delivery Notes & Shipping Labels <= 4.9.8 - Authenticated (Subscriber+) Arbitrary File Read via 'customer_note' ParameterSame generic ecosystem