LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25448: OrientDB 3.0.17 Stored Cross-Site Scripting via User Creation

OrientDB 3.0.17 contains a stored cross-site scripting vulnerability that allows authenticated attackers to inject malicious scripts by creating users with script payloads in the name parameter. Attackers can send POST requests to the document endpoint with JavaScript code in the name field to execute arbitrary scripts when users view the application.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-25448 is a stored cross-site scripting issue in OrientDB 3.0.17. An authenticated user can save script content in a user name field, causing script execution when the application displays it. Business impact is mainly compromised user sessions, data exposure, or unauthorized actions inside the OrientDB web interface.

Executive priority

Treat as a moderate-priority application security issue. Prioritize environments where OrientDB administration is internet-accessible, broadly shared, or used with privileged sessions. Remediation should focus on version review, access restriction, and vendor guidance.

Technical view

OrientDB 3.0.17 is affected by CWE-79 stored XSS via user creation. The CVSS 3.1 score is 6.4, with network access, low complexity, and low privileges required. The vulnerability is tied to the name parameter during user creation and can execute when viewed by application users.

Likely exposure

Exposure is most relevant where OrientDB 3.0.17 is deployed and authenticated users can create or modify users through the web application. Internet-facing consoles or shared administrative environments increase practical risk.

Exploitation context

A public ExploitDB reference exists, but the source bundle does not show confirmed active exploitation, and KEV status is false. Exploitation requires authenticated access, but stored XSS can affect later viewers of the application.

Researcher notes

Evidence identifies OrientDB 3.0.17 and stored XSS through user creation. The provided sources do not name a fixed version or official patch. Avoid assuming broader version impact without vendor confirmation.

Mitigation direction

  • Identify any OrientDB 3.0.17 deployments.
  • Check OrientDB vendor guidance for fixed versions or official remediation.
  • Restrict access to OrientDB administrative interfaces.
  • Limit user-creation privileges to trusted administrators.
  • Monitor for suspicious user names or unexpected script-like content.

Validation and detection

  • Confirm the deployed OrientDB version.
  • Review whether the web interface is reachable from untrusted networks.
  • Audit accounts with user-creation or administrative privileges.
  • Inspect existing user records for abnormal script-like values.
  • Track vendor advisories for remediation status.
Prepared
Confidence
medium
Sources
5

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-25448 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
6.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N3.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.4Medium
CVSS 3.1 vector shape for CVE-2019-25448Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OrientdbOrientDB3.0.17Listed
Weakness

CWE details

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.