dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-24762

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Missing Authorization vulnerability in facturaone TicketBAI Facturas para WooCommerce wp-ticketbai allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects TicketBAI Facturas para WooCommerce: from n/a through <= 3.45.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Missing authorization vulnerability in the TicketBAI Facturas para WooCommerce plugin (wp-ticketbai) allows exploiting incorrectly configured access control security levels. The issue is exploitable over the network without authentication but requires user interaction. Attackers can potentially access functions or data that should require authorization.

MitigationUpdate the plugin to a version beyond 3.45 when available, or apply any security patches released by facturaone. Review and enforce proper access control configurations on affected endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify TicketBAI plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'TicketBAI Facturas para WooCommerce' or 'wp-ticketbai' in the list
    Affected if plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find the TicketBAI plugin, and note the version number displayed below the plugin name. Alternatively, inspect the plugin main file header in /wp-content/plugins/wp-ticketbai/
    Affected if version is 3.45 or lower (versions above 3.45 contain the fix)
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify the TicketBAI plugin shows as 'Active' (not deactivated)
    Affected if plugin is active and version is 3.45 or lower
  4. Inspect plugin endpoints for access control
    Review the plugin directory /wp-content/plugins/wp-ticketbai/ for PHP files handling API endpoints, AJAX actions, or admin pages. Check if these files include capability checks or nonce verification before processing requests
    Affected if endpoints lack proper authorization checks (require code review or penetration testing to confirm)

Environment is affected if the TicketBAI plugin is installed, active, and running version 3.45 or lower, as the missing authorization flaw allows unauthenticated network attackers to reach protected functions with user interaction.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 3.45 when available, or apply any security patches released by facturaone. Review and enforce proper access control configurations on affected endpoints.

Recommended fix Moderate confidence

Version greater than 3.45 (latest available version from the vendor)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'TicketBAI Facturas para WooCommerce' (wp-ticketbai)
  4. 4. If an update is available, click 'Update Now'
  5. 5. After updating, verify the plugin version is above 3.45
  6. 6. Test the TicketBAI functionality to ensure the authorization controls are working correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24762 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24762 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data