dbcve.org
Aria Operations For LogsApplication · VMware

CVE-2025-22219

CRITICAL · 9.0 CVSS v3.1 Published 2025-01-30
Fix available
A fix is available. Upgrade to 8.18.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

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
VMware Aria Operations for Logs contains a stored cross-site scripting vulnerability. A malicious actor with non-administrative privileges may be able to inject a malicious script that (can perform stored cross-site scripting) may lead to arbitrary operations as admin user.

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

VMware Aria Operations for Logs contains a stored cross-site scripting (XSS) vulnerability where an authenticated non-administrative user can inject malicious scripts into the application. When administrators access the affected interface, the injected script executes in their context, potentially allowing the attacker to perform arbitrary operations with admin privileges.

MitigationApply VMware's patch for CVE-2025-22219 when available. In the interim, minimize the number of non-administrative users, monitor for suspicious administrative activity, and consider network segmentation to limit exposure.

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
Aria Operations For LogsApplication
Affected:>= 8.0, < 8.18.3
Cloud FoundationApplication
Affected:>= 4.0, <= 5.2

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
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify installed VMware Aria Operations for Logs version
    Log into the VMware Aria Operations for Logs admin interface or use the command line: vROpsLogs/bin/vcopsLogAdmin.sh version (or check /usr/lib/vmware-vcops/user/conf/root/tomcat-conf/catalina.out for version info)
    Affected if The installed version is 8.0 or higher but lower than 8.18.3
  2. Identify VMware Cloud Foundation version if applicable
    Check the VMware Cloud Foundation version through the SDDC Manager interface or run: sudo /opt/vmware/sddc-support/sos --get-version
    Affected if The installed version is 4.0 through 5.2 inclusive (this includes the vulnerable Aria Operations for Logs component)
  3. Verify presence of non-administrative users
    In the Aria Operations for Logs web interface, navigate to Administration > Users and Roles, or use the API: GET /api/v2/users to list all configured users
    Affected if Any authenticated non-administrative users exist in the system (these could inject the XSS payload)
  4. Confirm web interface is accessible
    Attempt to reach the Aria Operations for Logs web UI at the configured hostname/IP on port 443, or verify the service is running: systemctl status vcopsLog
    Affected if The web interface is exposed and reachable (required for the XSS to be triggered when administrators access the affected interface)

The environment is affected if Aria Operations for Logs version is >= 8.0 and < 8.18.3 (or Cloud Foundation 4.0-5.2) AND non-administrative users have access to the web interface where they can inject stored XSS payloads that will execute when administrators view the affected interface.

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 8.18.3 or later
Fixed in 8.18.3
Interim mitigation

Apply VMware's patch for CVE-2025-22219 when available. In the interim, minimize the number of non-administrative users, monitor for suspicious administrative activity, and consider network segmentation to limit exposure.

Recommended fix High confidence

8.18.3 or later

  1. 1. Identify the current installed version of Aria Operations for Logs by accessing the administration interface or using the command line tool.
  2. 2. Review the upgrade requirements and prerequisites in the VMware Aria Operations for Logs 8.18.3 release notes.
  3. 3. Create a complete backup of the current Aria Operations for Logs configuration and data.
  4. 4. Schedule a maintenance window as upgrades may require downtime.
  5. 5. Download VMware Aria Operations for Logs version 8.18.3 or later from the Broadcom support portal.
  6. 6. Follow the official upgrade procedure documented in the VMware Aria Operations for Logs upgrade guide.
  7. 7. After upgrade, verify the installation by logging in and confirming all services are running.
  8. 8. Test that the XSS vulnerability is no longer reproducible by attempting to inject test scripts (in a non-production environment first).
Caveat Review release notes for any breaking changes between your current version and 8.18.3; some configurations or integrations may require adjustment

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

Fix this in Aria Operations For Logs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22219 — 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-22219 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