dbcve.org
VerticaApplication · Opentext

CVE-2025-12454

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 25.2.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in OpenText™ Vertica allows Reflected XSS.  The vulnerability could lead to Reflected XSS attack of cross-site scripting in Vertica management console application.This issue affects Vertica: from 10.0 through 10.X, from 11.0 through 11.X, from 12.0 through 12.X, from 23.0 through 23.X, from 24.0 through 24.X, from 25.1.0 through 25.1.X.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Reflected XSS vulnerability in OpenText Vertica management console where user-supplied input is not properly neutralized during web page generation, allowing injection of malicious scripts that execute in the context of the user's browser session.

MitigationApply vendor-provided patches for affected Vertica versions. Implement input validation and output encoding on all user-facing endpoints in the management console as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VerticaApplication
Affected:>= 10.0.0-0, < 25.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Vertica installation exists
    Identify if Vertica is installed on the system. Check for /opt/vertica directory, running vertica processes, or installed packages. Common installation paths include /opt/vertica/. Query the database with 'vsql -c "SELECT VERSION();"' if credentials are available.
    Affected if Vertica database software is installed on the system
  2. Determine installed Vertica version
    Run 'vertica -V' from the Vertica bin directory, or check the VERSION file in /opt/vertica/, or query: SELECT VERSION();
    Affected if Installed version is 10.0.0-0 or higher but below 25.2.0
  3. Confirm Management Console is accessible
    Check if the Management Console service is running and accessible. The MC typically listens on ports 5444 (HTTPS) or 5434 (HTTP). Use 'netstat -tlnp | grep -E "5444|5434"' or 'ss -tlnp | grep -E "5444|5434"' to check if these ports are listening.
    Affected if Management Console port is open and accepting connections
  4. Check Management Console exposure
    Evaluate whether the Management Console web interface is accessible to untrusted users or networks. Verify network binding configuration and any access control lists. The vulnerability is exploitable when a user clicks a crafted malicious link to the MC interface.
    Affected if Management Console is accessible to untrusted users or untrusted networks and version is in affected range

User is affected if Vertica version is 10.0.0-0 or higher but below 25.2.0 AND the Management Console is accessible (even internally), since the reflected XSS executes in the context of a legitimate user's browser session.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 25.2.0 or later
Fixed in 25.2.0
Interim mitigation

Apply vendor-provided patches for affected Vertica versions. Implement input validation and output encoding on all user-facing endpoints in the management console as a defense-in-depth measure.

Recommended fix High confidence

25.2.0 or later

  1. Download Vertica version 25.2.0 or later from the OpenText/Vertica portal
  2. Perform a full backup of your Vertica database before upgrading
  3. Stop all Vertica services on the node(s) being upgraded
  4. Upgrade Vertica to version 25.2.0 or later using the standard upgrade procedure for your deployment type (in-place or rolling upgrade)
  5. Start Vertica services and verify the upgrade completed successfully
  6. Access the Vertica Management Console and verify the XSS vulnerability in reflected parameters has been remediated
Caveat Review Vertica 25.2.0 release notes for any database compatibility changes, configuration adjustments, or deprecated features before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vertica Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12454 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data