dbcve.org
Webaccess\/vpnApplication · Advantech

CVE-2025-34244

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 AjaxFwRulesController.ajaxDeviceFwRulesAction() 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 AjaxFwRulesController.ajaxDeviceFwRulesAction() method. An authenticated user with low 'observer' privilege can inject malicious SQL code through datatable search parameters to exfiltrate sensitive database information.

MitigationUpgrade to WebAccess/VPN version 1.1.5 or later which contains the vendor fix for 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 if Advantech WebAccess/VPN is installed
    Check for WebAccess/VPN installation directories, running services, or the web interface typically accessible on ports 80/443 or custom ports. Look for installation paths such as C:\Program Files\Advantech\WebAccess\VPN or /opt/advantech/webaccess/vpn.
    Affected if The application is present on the system and the web interface is accessible.
  2. Determine the installed WebAccess/VPN version
    Locate version information in the installation directory, typically in a version.txt, about.ini, or manifest file. Alternatively, access the login page and check any version display in the UI footer or error pages.
    Affected if The installed version is any version prior to 1.1.5 (e.g., 1.1.4, 1.1.3, 1.0.x, etc.).
  3. Verify the AjaxFwRulesController endpoint is accessible
    Attempt to access the vulnerable endpoint path typically at /Ajax/AjaxFwRulesController.ajax or similar paths under the web application root. Use a web browser or curl to send a request to this endpoint.
    Affected if The endpoint responds (even with an authentication redirect) indicating the vulnerable controller is present and loaded.
  4. Confirm authentication is enabled for the web interface
    Check the web server configuration or authentication settings within WebAccess/VPN to verify that user authentication is required. Try accessing the login page and confirm credentials are required.
    Affected if The web interface requires authentication, which allows low-privilege 'observer' users to authenticate and reach the vulnerable function.

You are affected if Advantech WebAccess/VPN is installed with a version prior to 1.1.5 and the web interface with user authentication is enabled, allowing authenticated 'observer' users to reach the AjaxFwRulesController endpoint.

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 vendor fix for this SQL injection vulnerability.

Recommended fix High confidence

WebAccess/VPN version 1.1.5

  1. 1. Identify current WebAccess/VPN version by checking the system dashboard or using the built-in version check command
  2. 2. Download WebAccess/VPN version 1.1.5 from the official Advantech download portal or support site (icr.advantech.com)
  3. 3. Create a full backup of the current system configuration and database
  4. 4. Stop all WebAccess/VPN services before applying the upgrade
  5. 5. Install version 1.1.5 using the official upgrade procedure documented in the installation guide
  6. 6. Verify the upgrade was successful by checking the new version number
  7. 7. Restart WebAccess/VPN services
  8. 8. Log in and verify the AjaxFwRulesController functionality is working properly
Caveat Standard upgrade - review release notes for any configuration changes required; test in non-production environment first

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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-34244 — 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-34244 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