dbcve.org
Webaccess\/vpnApplication · Advantech

CVE-2025-34241

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 AjaxDeviceController.ajaxDeviceAction() 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 the AjaxDeviceController.ajaxDeviceAction() method. Authenticated low-privileged observer users can inject malicious SQL code through datatable search parameters, enabling disclosure of sensitive database information.

MitigationUpgrade to WebAccess/VPN version 1.1.5 or later to obtain the patched code. If immediate patching is not feasible, implement strict input validation on datatable search parameters and restrict observer-level accounts to minimize attack surface.

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 WebAccess/VPN installation directory and check version file, or access the application's About/Version page through the web interface. Compare the version number to the affected range (prior to 1.1.5).
    Affected if Version is below 1.1.5
  2. Verify AjaxDeviceController endpoint exists
    Check the application web root for the AjaxDeviceController class or servlet. On the running application, attempt to access the ajaxDeviceAction endpoint (typically at /AjaxDeviceController/ajaxDeviceAction or similar path under the webapp).
    Affected if The AjaxDeviceController.ajaxDeviceAction endpoint is present and responds to requests
  3. Confirm observer-level accounts are present
    Review user management section or user database/table to identify accounts with observer or low-privilege roles. These are the accounts that can exploit the SQL injection.
    Affected if At least one observer-level or low-privilege user account exists in the system
  4. Check datatable search parameter handling
    Inspect the application's request handling for datatable search parameters. Submit a test request to any datatable-enabled page (such as device listings) with SQL wildcard characters in search fields to observe if input is passed directly to SQL queries without sanitization.
    Affected if Datatable search parameters are accepted and processed without parameterized query handling

Your environment is affected if WebAccess/VPN version is below 1.1.5 AND the AjaxDeviceController endpoint is accessible AND observer-level accounts exist with access to datatable search functionality.

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 to obtain the patched code. If immediate patching is not feasible, implement strict input validation on datatable search parameters and restrict observer-level accounts to minimize attack surface.

Recommended fix High confidence

WebAccess/VPN 1.1.5

  1. 1. Identify the current version of Advantech WebAccess/VPN by accessing the administration interface or checking system information
  2. 2. Create a complete backup of the current WebAccess/VPN configuration and database
  3. 3. Download the WebAccess/VPN version 1.1.5 or later from the official Advantech support portal (icr.advantech.com)
  4. 4. Follow the official upgrade procedure documented in the WebAccess/VPN installation/administration guide
  5. 5. After upgrading, verify the AjaxDeviceController.ajaxDeviceAction() endpoint is no longer vulnerable by testing with the datatable search parameters
  6. 6. Confirm all users, especially low-privileged observer accounts, can still authenticate and perform authorized operations

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
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
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,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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