Passster < 4.2.24 - Password Protection Bypass

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/Passster (generic). Check affected ranges and fixed versions before updating.

Recommended response

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

Evidence timeline and material changes

1. Published upstream

   Sep 2, 2026

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

2. Source modified

   Sep 2, 2026

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

3. First seen by HOL

   Sep 2, 2026

Sources and claim methodology

• Source referencewpscan.com

Related CVEs

• Passster < 4.2.26 - Global Protection BypassSame unknown/passster package
• Wp Edit Password Protected < 1.3.5 - Protection Bypass via REST APIAlso CWE-863
• Restrict User Access 2.6 - 2.8 - Unauthenticated Content Protection Bypass via REST API Route NormalizationAlso CWE-863
• Incorrect Authorization in Fleet Server Leading to Denial of Service of Agent Upload OperationsAlso CWE-863
• Incorrect Authorization in Kibana Leading to Unauthorized Cross-Space Exposure of Machine Learning Job DataAlso CWE-863
• Incorrect Authorization in Elastic Cloud on Kubernetes Leading to Unauthorized Modification of DataAlso CWE-863