Security readout for executives and security teams
Plain-English summary
CVE-2025-50341 is reported as a critical SQL injection issue in Axelor 5.2.4. A remote attacker may be able to alter database query logic through the _domain parameter, creating risk of data exposure, data change, or service impact. The public record is sparse, so confirm local exposure before taking disruptive action.
Executive priority
Prioritize this as a near-term critical exposure review. If Axelor 5.2.4 is internet-facing, treat remediation or isolation as urgent because the vulnerability may affect database confidentiality, integrity, and availability without requiring authentication per CVSS.
Technical view
The CVE describes Boolean-based SQL injection via the _domain parameter in Axelor 5.2.4. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. The stated impact is high confidentiality, integrity, and availability loss. Affected-product metadata in the CVE bundle is incomplete.
Likely exposure
Likely exposure is limited to environments running Axelor 5.2.4, especially internet-reachable instances or systems with untrusted access to affected application routes. The CVE affected field lists n/a, so product and version scope should be validated against vendor or project guidance.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. A public GitHub reference exists, but the provided sources do not establish exploitation in the wild. Treat as urgent because the CVSS score and attack prerequisites indicate high potential impact if reachable.
Researcher notes
Evidence is limited: the CVE names Axelor 5.2.4, but affected-product metadata is n/a and no official patch is identified in the bundle. Validate route reachability, authentication assumptions, database privileges, and fixed-version availability before writing detections or closure criteria.
Mitigation direction
- Identify any Axelor 5.2.4 deployments and prioritize exposed instances.
- Check Axelor or project guidance for a fixed release or official workaround.
- Restrict public access to affected Axelor routes where business permits.
- Review database account privileges used by Axelor and reduce unnecessary rights.
- Increase monitoring for unusual query errors, parameter probing, or data-access anomalies.
Validation and detection
- Confirm whether Axelor 5.2.4 is present in production, staging, or customer environments.
- Map exposed Axelor endpoints that accept or process the _domain parameter.
- Review access logs for suspicious _domain activity without replaying exploit patterns.
- Check vulnerability scanners and SBOM records for Axelor version evidence.
- Track CVE and GitHub reference updates for corrected affected-version details.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration 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-50341 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/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.
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:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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://github.com/millad7/Axelor-vulnerability-CVE-2025-50341CVE reference, mitre
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 Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.