CVE-2019-25449: OrientDB 3.0.17 Reflected Cross-Site Scripting via document endpoint
OrientDB 3.0.17 contains a reflected cross-site scripting vulnerability that allows attackers to inject malicious scripts by submitting crafted JSON payloads to the document endpoint. Attackers can send POST requests to /document/demodb/-1:-1 with script tags in the name parameter to execute arbitrary JavaScript in users' browsers.
Security readout for executives and security teams
Plain-English summary
OrientDB 3.0.17 has a reflected cross-site scripting issue. A malicious request can cause JavaScript to run in a user's browser when they interact with the affected document endpoint. This is not a server takeover by itself, but it can expose user data or actions in the browser context.
Executive priority
Treat as a moderate-priority web application risk. Prioritize systems exposed to users or the internet, but do not displace critical remote code execution or actively exploited vulnerabilities unless OrientDB is business-critical or externally accessible.
Technical view
CVE-2019-25449 is CWE-79 reflected XSS in OrientDB 3.0.17 document endpoint JSON handling. The supplied CVSS 3.1 score is 6.1: network reachable, low complexity, no privileges, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.
Likely exposure
Exposure is limited to environments running OrientDB 3.0.17, especially where the web interface or document endpoint is reachable by users or untrusted networks. The source bundle does not name other affected versions, forks, hosted services, or dependent products.
Exploitation context
The bundle includes an ExploitDB reference, so public exploit information exists. The CVE is not marked KEV, and the provided sources do not establish active exploitation in the wild. User interaction is required for browser-side impact.
Researcher notes
Evidence is sufficient for affected product, version, vulnerability class, and public exploit availability. Evidence is incomplete for patched versions, official mitigation, and real-world exploitation. Avoid broad version assumptions beyond OrientDB 3.0.17.
Mitigation direction
Inventory OrientDB deployments and identify any version 3.0.17 instances.
Check OrientDB guidance for a fixed version or official workaround.
Restrict OrientDB web access to trusted administrators and networks.
Reduce exposure of affected endpoints from the public internet.
Monitor for unexpected script-like input in document endpoint activity.
Validation and detection
Confirm whether OrientDB 3.0.17 is deployed in production or test environments.
Verify who can reach the OrientDB web/document endpoint.
Review application logs for suspicious document endpoint submissions.
Check whether vendor guidance or an upgrade has already been applied.
Assess whether browser sessions have sensitive administrative access.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-79: 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.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.