Security readout for executives and security teams
Plain-English summary
CVE-2025-26965 is an access-control weakness in the WordPress Amelia booking plugin through version 1.2.16. An unauthenticated remote actor may influence a user-controlled object reference and make unauthorized low-impact changes. The published CVSS score is medium, with integrity impact only and no stated confidentiality or availability impact.
Executive priority
Treat this as a moderate-priority WordPress plugin risk. It is remotely reachable and unauthenticated, but the cited impact is limited to integrity and the bundle provides no active exploitation evidence. Prioritize public booking sites and update or disable affected deployments based on vendor guidance.
Technical view
The issue is CWE-639, an IDOR-style authorization bypass through a user-controlled key in ameliabooking Amelia. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, indicating remote, unauthenticated, low-complexity exploitation with limited integrity impact. Public details in the supplied sources do not name affected endpoints or a fixed version.
Likely exposure
Exposure is likely limited to WordPress sites running the Amelia/ameliabooking plugin at version 1.2.16 or earlier. Internet-facing booking sites are more relevant because the CVSS vector requires only network access and no authentication. The bundle does not identify other products or platforms.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. Public exploitability detail is sparse: the records identify the class, affected version range, and CVSS vector, but not endpoints, payloads, or observed attacks.
Researcher notes
Evidence supports an IDOR/CWE-639 issue affecting Amelia through 1.2.16. The CVSS vector is the strongest technical signal. The bundle does not provide endpoint-level details, a confirmed fixed release, proof-of-concept status, or telemetry showing exploitation, so avoid assumptions beyond unauthorized low-integrity modification risk.
Mitigation direction
- Inventory WordPress sites for Amelia/ameliabooking installations.
- Prioritize sites running Amelia version 1.2.16 or earlier.
- Check Amelia vendor and Patchstack guidance for a fixed version or mitigation.
- Update, disable, or restrict the plugin if no supported fix is available.
- Review booking data for unauthorized low-integrity changes.
Validation and detection
- Confirm installed plugin name and version from WordPress administration or asset inventory.
- Compare installed versions against the affected range: through 1.2.16.
- Review application logs for unusual unauthenticated Amelia-related activity.
- Validate authorization behavior in a controlled staging environment only.
- Document whether the site exposes booking functionality to the internet.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-26965 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.