CVE-2025-12017: VNPAY Payment gateway (WordPress plugin) · Cross-site Scripting
Affects VNPAY Payment gateway (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| teyldoan VNPAY Payment gateway | Affected
| Fixed in– |
AI-suggested
Users of the VNPAY Payment gateway plugin should monitor the vendor's advisory channels for updates. Until a fix is available, administrators should consider disabling or restricting access to the vulnerable plugin or implementing web application firewall (WAF) rules to detect and block malicious payloads targeting the 'message' parameter. Avoiding user interaction with suspicious links can reduce risk.
Description
The VNPAY Payment gateway plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'message' parameter in all versions up to, and including, 1.0.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.