dbcve.org
Webaccess\/vpnApplication · Advantech

CVE-2025-34246

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-06
Fix available
A fix is available. Upgrade to 1.1.5 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Advantech WebAccess/VPN versions prior to 1.1.5 contain a SQL injection vulnerability in AjaxPrevalidationController.ajaxAction() that allows an authenticated low-privileged observer user to inject SQL via datatable search parameters, leading to disclosure of database information.

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

Advantech WebAccess/VPN versions prior to 1.1.5 contain a SQL injection vulnerability in the AjaxPrevalidationController.ajaxAction() method. An authenticated low-privileged observer user can inject malicious SQL code through datatable search parameters, potentially allowing disclosure of sensitive database information.

MitigationUpgrade to WebAccess/VPN version 1.1.5 or later. If immediate patching is not feasible, implement strict input validation and parameterization of database queries in the affected component as a compensating control.

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
Webaccess\/vpnApplication
Affected:< 1.1.5

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Identify installed WebAccess/VPN version
    Check the application interface or configuration files for the current version number. This is typically displayed in the software's About section, main dashboard, or versioninfo configuration file within the installation directory.
    Affected if The installed version is any release prior to 1.1.5 (for example, 1.1.4, 1.1.3, 1.0.x, etc.)
  2. Verify AjaxPrevalidationController accessibility
    Locate and inspect the AjaxPrevalidationController component within the application's web directory structure. Confirm the ajaxAction() method exists in the codebase or is accessible via the application's URL routing.
    Affected if The AjaxPrevalidationController component with the ajaxAction() method is present and exposed in the application
  3. Confirm datatable search feature is enabled
    Check if the application includes datatable components that support search/filter functionality. This feature is typically used in report views, log viewers, or data display pages within the web interface.
    Affected if Datatable search functionality is available and accepts user-supplied input without explicit parameterization
  4. Verify observer-level user access exists
    Check the application's user role configuration to confirm that low-privileged observer accounts can be created or exist. Attempt to log in with an observer-level account to validate access to the affected component.
    Affected if Low-privileged observer users can authenticate and access the datatable search features within AjaxPrevalidationController

The environment is affected if WebAccess/VPN version is below 1.1.5 AND the AjaxPrevalidationController with datatable search is accessible to authenticated users including low-privileged observer accounts.

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

Upgrade to WebAccess/VPN version 1.1.5 or later. If immediate patching is not feasible, implement strict input validation and parameterization of database queries in the affected component as a compensating control.

Recommended fix High confidence

1.1.5

  1. Identify the current installed version of Advantech WebAccess/VPN
  2. Obtain version 1.1.5 of Advantech WebAccess/VPN from the official Advantech download repository (icr.advantech.com)
  3. Review Advantech upgrade documentation before proceeding
  4. Back up the current WebAccess/VPN configuration and database
  5. Apply the upgrade to version 1.1.5 following vendor installation instructions
  6. Verify the installation was successful and the version is correct
  7. Confirm the SQL injection vulnerability is no longer present

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

Fix this in Webaccess\/vpn 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 the upgrade done

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-34246 — 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-34246 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