CVE-2024-11271

WordPress Webinar Plugin – WebinarPress <= 1.33.24 - Missing Authorization to Authenticated (Subscriber+) Webinar Updates

2025-01-07 00:00
Lucio Sá

Strategic Overview

Status
Patched in 1.33.25
Affected Plugin
WebinarPress – Webinar System for WordPress
Affected Version
<= 1.33.24
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-11271
View all WebinarPress – Webinar System for WordPress vulnerabilities

At a glance

CVE-2024-11271 is a high-severity Missing Authorization vulnerability in the WebinarPress WordPress plugin, affecting versions <= 1.33.24. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.33.25; sites on affected versions should update now. Disclosed January 2025, reported by Lucio Sá.

Vulnerability Overview

The WordPress Webinar Plugin – WebinarPress plugin for WordPress is vulnerable to modification of data due to a missing capability check on several functions in all versions up to, and including, 1.33.24. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify webinars.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in WebinarPress <= 1.33.24 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WebinarPress the fix is 1.33.25: builds <= 1.33.24 are affected, anything from 1.33.25 onward is not.

Remediation

Update to version 1.33.25, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WebinarPress 1.33.25 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-11271https://www.wordfence.com/threat-intel/vulnerabilities/id/88508dbd-b7a0-441d-918b-f4cb7a7cd000https://nvd.nist.gov/vuln/detail/CVE-2024-11271

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C