dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-26264

HIGH · 8.8 CVSS v3.1 Published 2025-02-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
GeoVision GV-ASWeb with the version 6.1.2.0 or less (fixed in 6.2.0), contains a Remote Code Execution (RCE) vulnerability within its Notification Settings feature. An authenticated attacker with "System Settings" privileges in ASWeb can exploit this flaw to execute arbitrary commands on the server, leading to a full system compromise.

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 · high confidence

GeoVision GV-ASWeb versions 6.1.2.0 and below contain an authenticated Remote Code Execution vulnerability in the Notification Settings feature. An attacker with System Settings privileges can inject and execute arbitrary operating system commands on the underlying server by exploiting insufficient input validation, potentially achieving full system compromise.

MitigationUpgrade GV-ASWeb to version 6.2.0 or later. Until patched, restrict administrative access to trusted personnel only and monitor for suspicious notification configuration changes.

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

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 GV-ASWeb installation and version
    Locate the GV-ASWeb application on the system and determine its installed version number. Common locations include the installation directory or the application's About/Status page.
    Affected if The installed version is 6.1.2.0 or lower
  2. Confirm the Notification Settings feature is present
    Access the GV-ASWeb administrative interface and navigate to the Notification Settings configuration area to verify the feature is enabled and accessible.
    Affected if The Notification Settings feature is available in the web interface
  3. Verify user privilege level
    Check the account privileges assigned to the user account in use. Look for System Settings or administrative-level permissions within GV-ASWeb.
    Affected if The account has System Settings privileges or administrative access
  4. Compare version against vulnerable range
    Compare your confirmed installed version against the affected range (6.1.2.0 and below). Any version at or below 6.1.2.0 is vulnerable.
    Affected if The installed version is 6.1.2.0 or any earlier version

You are affected if GV-ASWeb version 6.1.2.0 or below is installed and the Notification Settings feature is accessible with System Settings privileges.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade GV-ASWeb to version 6.2.0 or later. Until patched, restrict administrative access to trusted personnel only and monitor for suspicious notification configuration changes.

Recommended fix High confidence

GV-ASWeb version 6.2.0

  1. 1. Verify the current GV-ASWeb version by accessing the system administration interface
  2. 2. Confirm the installed version is 6.1.2.0 or earlier
  3. 3. Create a full backup of the GV-ASWeb configuration and database
  4. 4. Download GV-ASWeb version 6.2.0 or later from the official GeoVision website (www.geovision.com.tw)
  5. 5. Stop the GV-ASWeb service before applying the update
  6. 6. Install version 6.2.0 following the vendor's upgrade documentation
  7. 7. After upgrade, verify the Notification Settings feature functions correctly
  8. 8. Confirm the new version is reflected in the system information
Caveat Review GeoVision release notes for any configuration or feature changes between 6.1.2.0 and 6.2.0 before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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