Skip to main content
CVE-2025-34246VulnerabilityPublished Updated

CVE-2025-34246: Advantech WebAccess/VPN · SQL Injection

Affects Advantech WebAccess/VPNSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Advantech WebAccess/VPNAffected
  • =0
Fixed in–

AI-suggested

1. Upgrade Advantech WebAccess/VPN to version 1.1.5 or later where the vulnerability is patched. 2. Restrict observer user privileges strictly to the minimum necessary and review account assignments regularly. 3. Implement strong authentication mechanisms and enforce complex passwords for all user roles, especially low-privileged accounts. 4. Deploy web application firewalls (WAF) with tailored rules to detect and block SQL injection attempts targeting the AjaxPrevalidationController.ajaxAction() endpoint. 5. Monitor application logs and database query logs for unusual or suspicious patterns indicative of SQL injection exploitation. 6. Conduct regular security assessments and penetration testing focused on web application inputs and authentication controls. 7. Segment network access to the WebAccess/VPN interface, limiting it to trusted hosts and networks. 8. Educate administrators and users about the risks of SQL injection and the importance of secure credential management. 9. If patching is delayed, consider disabling or restricting the vulnerable AjaxPrevalidationController.ajaxAction() functionality if feasible without disrupting operations.

Description

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

References

Community reviews

Loading reviews…