dbcve.org
Webaccess\/vpnApplication · Advantech

CVE-2025-34245

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 AjaxStandaloneVpnClientsController.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 AjaxStandaloneVpnClientsController.ajaxAction() method. An authenticated low-privileged observer user can inject malicious SQL code through datatable search parameters, potentially exposing sensitive database information.

MitigationUpgrade Advantech WebAccess/VPN to version 1.1.5 or later to remediate this SQL injection vulnerability.

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
    Locate the version number through the product UI (typically in Help > About or System Information), check installer logs, or examine version files in the installation directory. Common paths may include C:\Program Files\Advantech\WebAccess\vpn\ or similar installation folders.
    Affected if The installed version is any release prior to 1.1.5 (e.g., 1.1.4, 1.1.3, 1.0.x)
  2. Verify VPN client management interface is accessible
    Confirm the AjaxStandaloneVpnClientsController endpoint is present and reachable. This typically appears under the VPN client management or monitoring section of the web interface. Attempt to access the endpoint via browser or HTTP request.
    Affected if The /VpnClients or /AjaxStandaloneVpnClientsController route is accessible and responds to requests
  3. Confirm observer or low-privilege accounts exist
    Review user roles and permissions in the WebAccess/VPN administration panel. Check if any users are assigned the 'observer' role or a similarly low-privilege permission level that grants login access without administrative rights.
    Affected if There are active user accounts with observer or low-privileged roles that can authenticate to the application
  4. Verify datatable search functionality is available to low-privilege users
    Log in with a low-privilege observer account and navigate to the VPN client management view. Test whether the datatable search/filter parameters are functional and can be modified through the web interface.
    Affected if Low-privileged users can access the VPN client datatable and submit search queries

A defender is affected if Advantech WebAccess/VPN is installed at a version below 1.1.5, the VPN client management interface is accessible, and low-privileged observer users can authenticate and interact with datatable search parameters.

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 Advantech WebAccess/VPN to version 1.1.5 or later to remediate this SQL injection vulnerability.

Recommended fix High confidence

1.1.5 or later

  1. 1. Identify the current installed version of Advantech WebAccess/VPN
  2. 2. Confirm the version is less than 1.1.5 to verify vulnerability status
  3. 3. Obtain the WebAccess/VPN version 1.1.5 or later from the official Advantech source
  4. 4. Backup the current configuration and database
  5. 5. Apply the upgrade following Advantech's standard upgrade procedure for WebAccess/VPN
  6. 6. Verify the upgrade was successful by checking the new version number
  7. 7. Test that the AjaxStandaloneVpnClientsController functionality works correctly
  8. 8. Verify the SQL injection vulnerability is remediated by attempting the original attack vector with valid observer credentials
Caveat Review release notes for any configuration changes or feature modifications between current version and 1.1.5

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

Fix this in Webaccess\/vpn Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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