Security readout for executives and security teams
Plain-English summary
CVE-2026-24963 affects the WordPress Amelia booking plugin through version 1.2.38. The flaw can allow privilege escalation due to incorrect privilege assignment. Business risk is highest for WordPress sites using Amelia with many privileged users or weak administrator controls. No provided source confirms active exploitation.
Executive priority
Treat as high priority for WordPress environments using Amelia, especially on revenue-generating booking sites. The flaw requires high privileges, so prioritize sites with many admins, shared credentials, or recent account compromise concerns. If Amelia is not present, this CVE is not directly applicable.
Technical view
The CVE describes CWE-266 in ameliabooking Amelia, affecting versions through 1.2.38. CVSS 3.1 is 7.2: network-accessible, low complexity, high privileges required, no user interaction, with high confidentiality, integrity, and availability impact. The provided sources do not name a fixed version or disclose exploit details.
Likely exposure
Exposure is limited to WordPress installations running the Amelia plugin at version 1.2.38 or earlier. The CVSS vector indicates an attacker needs high privileges already, reducing broad internet risk but increasing concern for compromised admin accounts, shared administrator access, or insider misuse.
Exploitation context
The source bundle does not show CISA KEV listing or any cited confirmation of active exploitation. Patchstack and CVE references identify the vulnerability class and affected versions, but no weaponized details or observed exploitation evidence are provided here.
Researcher notes
Key evidence is sparse. CVSS indicates PR:H despite privilege escalation, so exploitation likely depends on already privileged access. The bundle does not provide a patch version, proof of exploitation, or technical root-cause details beyond incorrect privilege assignment in Amelia through 1.2.38.
Mitigation direction
- Inventory WordPress sites for the Amelia plugin and version.
- Check vendor and Patchstack guidance for a fixed release or official workaround.
- Update Amelia when a vendor-supported fixed version is available.
- Remove or disable Amelia where it is not business-critical.
- Restrict high-privilege WordPress accounts to trusted administrators only.
- Review recent administrator account, role, and plugin-setting changes.
Validation and detection
- Confirm Amelia is installed on each WordPress site.
- Record the installed Amelia version and compare against <= 1.2.38.
- Verify whether vendor guidance identifies a fixed version.
- Audit privileged WordPress users for unnecessary access.
- Review logs for unexpected role or administrator changes.
- Confirm removed, disabled, or updated plugin status after remediation.
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-266: 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-2026-24963 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
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
Incorrect Privilege Assignment
Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.