Security readout for executives and security teams
Plain-English summary
Eramba v3.26.0 may trust malicious websites as if they were approved browser origins. If an authenticated user’s browser reaches an affected Eramba API, sensitive session details could be exposed to attacker-controlled JavaScript.
Executive priority
Treat as a moderate-priority confidentiality issue. Prioritize internet-accessible or broadly user-accessible Eramba deployments because exposed session data can support account compromise or sensitive governance data disclosure.
Technical view
The issue is a CORS policy flaw: attacker-controlled Origin values are reflected in Access-Control-Allow-Origin while Access-Control-Allow-Credentials is true. The source names Eramba Community and Enterprise Editions v3.26.0 and API paths such as /system-api/login and /system-api/user/me. CWE-942 applies.
Likely exposure
Likely limited to Eramba Community or Enterprise Edition v3.26.0 deployments with browser-accessible API sessions. The bundle says default installations are affected and v3.23.3 and earlier appeared unaffected. No CPEs are provided.
Exploitation context
No KEV listing or cited source confirms active exploitation. The CVSS vector requires user interaction, while the description says no user interaction; that inconsistency should be validated against vendor guidance.
Researcher notes
Evidence is limited to the CVE description and one Eramba release reference. The affected-product metadata is incomplete, and fix status is not explicit in the bundle. Validate version impact and remediation directly with Eramba.
Mitigation direction
- Review Eramba’s release 3.28.0 notice and current vendor guidance.
- Upgrade or apply vendor-provided remediation if Eramba confirms a fixed release.
- Restrict Eramba API access to trusted networks where operationally feasible.
- Review CORS settings for exact trusted origins and credential handling.
- Monitor Eramba sessions for suspicious API access patterns.
Validation and detection
- Inventory Eramba Community and Enterprise deployments and confirm versions.
- Check whether any deployment is running v3.26.0.
- Confirm browser clients receive only approved Access-Control-Allow-Origin values.
- Verify Access-Control-Allow-Credentials is not paired with reflected untrusted origins.
- Review logs for unexpected origins accessing system-api endpoints.
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-942: 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-2025-55462 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
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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://discussions.eramba.org/t/release-3-28-0/7860CVE 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.
Permissive Cross-domain Security Policy with Untrusted Domains
Permissive Cross-domain Security Policy with Untrusted Domains represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.