dbcve.org
Webaccess\/vpnApplication · Advantech

CVE-2025-34242

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 AjaxNetworkController.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 · moderate confidence

Advantech WebAccess/VPN versions prior to 1.1.5 contain a SQL injection vulnerability in AjaxNetworkController.ajaxAction() that allows an authenticated low-privileged observer user to inject malicious SQL via datatable search parameters, leading to disclosure of sensitive database information.

MitigationUpgrade to WebAccess/VPN version 1.1.5 or later which contains the security fix. Until then, implement strict input validation on datatable search parameters and apply the principle of least privilege to user accounts.

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 and read the version information for Advantech WebAccess/VPN installation, typically found in the application properties, about page, or installation metadata
    Affected if The installed version is prior to 1.1.5 (e.g., 1.1.4, 1.1.3, etc.)
  2. Verify AjaxNetworkController component presence
    Confirm the AjaxNetworkController.ajaxAction() endpoint exists in the deployed WebAccess/VPN application
    Affected if The AjaxNetworkController component is present and exposed in the application
  3. Confirm user authentication is enabled
    Check that the WebAccess/VPN authentication system is active and user login functionality is operational
    Affected if Users can authenticate to the application, including low-privileged observer-level accounts
  4. Verify datatable search feature is accessible
    Check that datatable search functionality is available in the application interface, particularly within network-related views where AjaxNetworkController is used
    Affected if Datatable search parameters can be submitted through the application by authenticated users

Your environment is affected if WebAccess/VPN version is below 1.1.5, the AjaxNetworkController component is present, user authentication is enabled, and datatable search functionality is accessible to low-privileged observer users.

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 which contains the security fix. Until then, implement strict input validation on datatable search parameters and apply the principle of least privilege to user accounts.

Recommended fix Moderate confidence

WebAccess/VPN 1.1.5

  1. Upgrade Advantech WebAccess/VPN to version 1.1.5 or later
  2. After upgrading, verify the AjaxNetworkController.ajaxAction() component no longer accepts unsanitized SQL in datatable search parameters
  3. Confirm that observer-level users can no longer inject SQL via search parameters
  4. Test that legitimate datatable search functionality still works correctly post-upgrade

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

Fix this in Webaccess\/vpn 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-34242 — 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-34242 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