Security readout for executives and security teams
Plain-English summary
CVE-2025-66123 affects the WordPress BookPro plugin up to version 1.1.0. An unauthenticated attacker may be able to access another user’s object or record because the plugin does not properly enforce object-level authorization. The documented impact is limited confidentiality exposure, not data modification or service disruption.
Executive priority
Prioritize review for public WordPress sites using BookPro, especially where bookings or customer records may be present. This is not currently evidenced as actively exploited, but unauthenticated data exposure can create privacy, customer trust, and compliance concerns.
Technical view
The issue is an unauthenticated Insecure Direct Object Reference mapped to CWE-639 in About Envato BookPro / ovabookpro <= 1.1.0. CVSS 3.1 is 5.3: network exploitable, low complexity, no privileges, no user interaction, scope unchanged, low confidentiality impact, no integrity or availability impact.
Likely exposure
Exposure is limited to WordPress sites running the BookPro / ovabookpro plugin at version 1.1.0 or earlier. The sources do not identify affected endpoints, data types, installation prevalence, or whether default configurations are vulnerable.
Exploitation context
The CVSS vector indicates remote unauthenticated exploitation is possible without user interaction. The source bundle does not report public exploitation, exploit availability, or CISA KEV listing. Treat this as a data exposure risk until the vendor or Patchstack provides more operational detail.
Researcher notes
Evidence is sparse. The public record identifies IDOR/CWE-639 and CVSS only, without endpoint details, proof of concept, patch version, or affected data fields. Avoid assuming impact beyond low confidentiality unless vendor advisories or further technical analysis confirm it.
Mitigation direction
Inventory WordPress sites for the BookPro / ovabookpro plugin.
Identify any installations running version 1.1.0 or earlier.
Check vendor and Patchstack guidance for an update or mitigation.
Restrict or disable the plugin if business risk exceeds tolerance.
Monitor web logs for unusual unauthenticated access patterns.
Validation and detection
Confirm plugin name, slug, and version from WordPress administration or asset inventory.
Review whether BookPro is internet-facing on production sites.
Check Patchstack and CVE records for updated remediation details.
Review access logs for suspicious requests to BookPro-related paths.
Document any potentially exposed data types for risk assessment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.