Security readout for executives and security teams
Plain-English summary
OrientDB 3.0.17 GA Community Edition has cross-site request forgery weaknesses in its web interface. If an authenticated user is tricked into interacting with attacker-controlled content, unauthorized database administration actions may be submitted. The business risk is unauthorized database, schema, user, or function changes where this version is used.
Executive priority
Treat as a moderate priority for teams using OrientDB 3.0.17. Prioritize internet-exposed or broadly accessible administrative interfaces. The main concern is unauthorized administrative change, not evidence of active mass exploitation from the provided sources.
Technical view
The CVE describes missing token validation affecting OrientDB endpoints including /database/, /command/, and /document/. Reported impact includes creating or deleting databases, modifying schema classes, managing users, and creating functions. The report also notes reflected and stored XSS in the web interface. CVSS v4.0 score is 5.3, severity medium.
Likely exposure
Exposure is likely limited to environments running OrientDB 3.0.17 GA Community Edition, especially where the web interface is reachable by administrators or database users. Risk increases if authenticated users can be socially engineered or if the interface is exposed beyond trusted networks.
Exploitation context
A public Exploit-DB entry is referenced, but the provided sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires an authenticated request context according to the CVSS vector and description. The issue is not described as unauthenticated remote compromise.
Researcher notes
Evidence is based on the CVE record, VulnCheck advisory, and a referenced Exploit-DB entry. The sources identify affected version 3.0.17 but do not provide a named fixed release in the supplied bundle. Avoid assuming other OrientDB versions are affected without vendor confirmation.
Mitigation direction
- Identify and prioritize any OrientDB 3.0.17 GA Community Edition instances.
- Check OrientDB vendor guidance for fixed versions or recommended remediation.
- Restrict OrientDB web interface access to trusted administrative networks.
- Limit administrative privileges for routine OrientDB users.
- Warn administrators not to browse untrusted sites while authenticated to OrientDB.
- Review exposure of affected endpoints and disable unnecessary web access where possible.
Validation and detection
- Confirm OrientDB product and version on all database hosts.
- Determine whether the web interface is enabled and network-reachable.
- Review user roles with database, schema, user, or function management privileges.
- Check audit logs for unexpected database, schema, user, or function changes.
- Verify whether vendor remediation has been applied once guidance is identified.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-2019-25447 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 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L
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:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
5.3MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-46517CVE reference · exploit
- OrientDB Official WebsiteCVE reference · product
- VulnCheck Advisory: OrientDB 3.0.17 Cross-Site Request ForgeryCVE reference · third-party-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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.