dbcve.org
Webaccess\/vpnApplication · Advantech

CVE-2025-34238

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 an absolute path traversal via AjaxStandaloneVpnClientsController.ajaxDownloadRoadWarriorConfigFileAction() that allows an authenticated network administrator to cause the application to read and return the contents of arbitrary files the web user (www-data) can access.

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 before 1.1.5 contain an absolute path traversal vulnerability in the AjaxStandaloneVpnClientsController.ajaxDownloadRoadWarriorConfigFileAction() method. An authenticated network administrator can manipulate the file path parameter to read arbitrary files accessible to the web server process (www-data), potentially exposing sensitive system files or configuration data.

MitigationUpgrade to WebAccess/VPN version 1.1.5 or later which contains the patch. If immediate upgrade is not feasible, implement strict input validation and path sanitization on the affected function to restrict file access to expected paths only.

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. Confirm Advantech WebAccess/VPN installation
    Locate the WebAccess/VPN application on the system. Common installation paths may include /opt/Advantech/WebAccess/VPN, C:\Program Files\Advantech\WebAccess\VPN, or check the system's service list for WebAccess/VPN processes.
    Affected if The product is present on the system.
  2. Determine installed WebAccess/VPN version
    Query the installed version through the application's interface, check version files in the installation directory, or use the command line tool if available (such as 'vpnserver version' or checking the About section in the web interface). Compare the version number to the affected range: versions before 1.1.5 are vulnerable.
    Affected if The installed version is less than 1.1.5.
  3. Verify the web server component is running
    Check if the WebAccess/VPN web service is active. On Linux, run 'ps aux | grep -i webaccess' or 'systemctl status webaccess-vpn'. On Windows, check the service status in Services.msc or use 'sc query WebAccessVPN'.
    Affected if The web server process is running and accessible over the network.
  4. Check if authentication is required for the vulnerable endpoint
    Attempt to access the AjaxStandaloneVpnClientsController.ajaxDownloadRoadWarriorConfigFileAction() endpoint without credentials, or review the application's authentication configuration to confirm whether network administrator credentials are enforced.
    Affected if The endpoint accepts requests without requiring valid administrator authentication (or if default/weak credentials are in use).

The environment is affected if Advantech WebAccess/VPN is installed with a version before 1.1.5 and the web interface is accessible, as an authenticated administrator could exploit the path traversal to read arbitrary files.

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 patch. If immediate upgrade is not feasible, implement strict input validation and path sanitization on the affected function to restrict file access to expected paths only.

Recommended fix High confidence

WebAccess/VPN 1.1.5

  1. Back up the current WebAccess/VPN configuration and any custom settings before proceeding with the upgrade.
  2. Obtain the WebAccess/VPN version 1.1.5 from the official Advantech source (icr.advantech.com or authorized distribution channels).
  3. Follow Advantech's standard upgrade procedure for WebAccess/VPN, typically involving stopping the service, replacing application files, and restarting the service.
  4. After upgrading, verify that the AjaxStandaloneVpnClientsController.ajaxDownloadRoadWarriorConfigFileAction() endpoint no longer accepts absolute path arguments and functions normally.
  5. Confirm the installation by checking the WebAccess/VPN version displayed in the administration interface shows 1.1.5 or later.

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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