Security readout for executives and security teams
Plain-English summary
A flaw in WSO2’s self-signup process can let an unauthenticated user place unchecked data into account claims. Downstream features may trust or display that data, potentially causing content manipulation, redirection, interface inconsistencies, unauthorized actions, or data exposure. Impact depends on whether self-signup is enabled and how claims are later consumed.
Executive priority
Treat as a targeted, moderate-priority review rather than an emergency. Prioritize internet-accessible identity or API deployments with self-signup enabled, especially where account claims influence authorization, redirects, or displayed content. Escalate if suspicious signup activity or unsafe downstream claim use is found.
Technical view
CVE-2024-10302 is a CWE-20 improper input-validation issue. It is remotely reachable without privileges or user interaction, but exploitation is rated high complexity. The CVSS 3.1 score is 4.0, with changed scope and low integrity impact; the supplied vector assigns no direct confidentiality or availability impact.
Likely exposure
Exposure is most likely where WSO2 user self-signup is enabled and downstream workflows consume signup-supplied claims. The bundle names several WSO2 products, but marks their listed product versions as unaffected and leaves the recovery component’s status unknown. Exact vulnerable version boundaries are therefore unclear from the supplied evidence.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as being in KEV. Exploitation requires no existing account or victim interaction, but is rated high complexity. Harm depends on downstream claim handling, so exposed signup alone does not establish practical impact.
Researcher notes
The bundle’s affected-version data is internally limited: named product versions are marked unaffected, while multiple recovery-component versions have unknown status. Do not infer affected release ranges from those entries. The described data-exposure and unauthorized-action outcomes are conditional, while the supplied CVSS vector scores low integrity impact and no direct confidentiality impact.
Mitigation direction
- Review the WSO2 advisory and obtain confirmed affected-version and remediation guidance.
- Inventory WSO2 deployments, versions, recovery components, and enabled self-signup features.
- Restrict or disable self-signup where operationally acceptable until exposure is confirmed.
- Validate and safely encode user-controlled claims before downstream processing.
- Apply vendor-provided fixes or updates after confirming product and version applicability.
Validation and detection
- Confirm whether public or tenant-level user self-signup is enabled.
- Identify workflows, redirects, interfaces, and authorization decisions consuming signup-created claims.
- Review recent signup records for unexpected, malformed, or policy-violating claim values.
- Verify installed recovery-component versions against current WSO2 advisory information.
- After remediation, confirm signup inputs cannot create unvalidated claim values.
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-20: 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 lookupCVE-2024-10302 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
- 4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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.
SSVC decision data
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:H/PR:N/UI:N/S:C/C:N/I:L/A:N2.21.4WSO2Vulnerability scoring details
Base CVSS 3.1 score
4MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3740/CVE reference, WSO2 · vendor-advisory
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.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.