WordPress ProLancer Element plugin <= 1.4.8 - Broken Access Control vulnerability

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

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for ThemeBing/ProLancer Element.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 24, 2026

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

2. Source modified

   Aug 24, 2026

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

3. First seen by HOL

   Aug 24, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• WordPress ProLancer Element plugin <= 1.4.8 - SQL Injection vulnerabilitySame themebing/prolancer element package
• WordPress Notification Master – Real-Time WordPress Notifications With Email, SMS, Webhooks & More plugin <= 1.7.1 - Broken Access Control vulnerabilityAlso CWE-862
• act 0.2.81 through 0.2.89 Missing Authorization in the Artifacts V4 BackendAlso CWE-862
• WordPress Booking and Rental Manager plugin <= 2.7.5 - Broken Access Control vulnerabilityAlso CWE-862
• WordPress Fluent Support Pro plugin <= 2.3.1 - Broken Access Control vulnerabilityAlso CWE-862
• IDOR and missing authorization in Prospero Flow CRM supplier API allows cross-tenant read and modificationAlso CWE-862