Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-6441 is a critical-severity Missing Authorization (CWE-862) vulnerability in Wordpress (inferred from references). Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 41% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The WebinarIgnition plugin for WordPress is affected by CVE-2025-6441, a missing capability check vulnerability in the webinarignition_sign_in_support_staff and webinarignition_register_support functions. All versions through 4.03.32 are impacted, allowing unauthenticated login token generation for arbitrary WordPress users and subsequent issuance of authorization cookies that bypass authentication. The flaw is tracked under CWE-862 and carries a CVSS 3.1 score of 9.8.
Unauthenticated attackers reachable over the network can invoke the affected AJAX endpoints without authentication or user interaction. Successful exploitation grants the ability to obtain valid login tokens and cookies for any targeted account, resulting in full authentication bypass and potential compromise of confidentiality, integrity, and availability.
The supplied references include a WordPress plugin repository changeset (3333177) that updates the affected files in class-webinarignition.php, class.WebinarignitionAjax.php, and class.WebinarignitionManager.php, indicating an official patch has been published.
EPSS remains flat at 0.0135 with no material increase since disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-22506
Vulnerability Data
The Webinar Solution: Create live/evergreen/automated/instant webinars, stream & Zoom Meetings | WebinarIgnition plugin for WordPress is vulnerable to unauthenticated login token generation due to a missing capability check on the `webinarignition_sign_in_support_staff` and `webinarignition_register_support` functions in all versions up to, and…
more
including, 4.03.32. This makes it possible for unauthenticated attackers to generate login tokens for arbitrary WordPress users under certain circumstances, issuing authorization cookies which can lead to authentication bypass.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Missing authorization in public WordPress plugin enables remote unauthenticated exploitation for auth bypass and valid account takeover.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces authorization checks on functions such as webinarignition_sign_in_support_staff before allowing login-token generation or cookie issuance.
Requires that privileged AJAX endpoints only execute with the minimum necessary privileges, blocking unauthenticated callers from obtaining arbitrary user tokens.
Mandates prompt application of the published patch (changeset 3333177) that adds the missing capability checks to class-webinarignition.php and related files.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Explicitly requires defining, enforcing, and reviewing authorizations and least privilege, directly preventing missing authorization checks.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requiring authentication and credentials before any access occurs eliminates the absence of authorization checks that would otherwise allow an unauthenticated actor to reach protected resources.
Requiring formal authorization of every access request before rights are granted ensures that checks for required permissions are performed, preventing missing authorization checks from being introduced.
Mandatory authorization checks and central records of granted rights ensure that every access attempt is preceded by an explicit decision rather than relying on missing checks.
Segregating the approval of access rights from their implementation provides an independent check that reduces the impact of missing authorization checks in the resulting system configuration.
By requiring competent outsiders to verify that every function enforces the need-to-know principle, the control lowers the likelihood that missing authorization checks persist undetected.
Defining authorization responsibilities and reviewing risk-treatment progress throughout the project lifecycle catches missing authorization checks before the system is deployed.