← WordPress Vulnerabilities
WordPress security by component

WPtouch

WPtouch is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published Jun 06, 2025; the highest CVE/CNA score is 8.8.

Plugin slug: wptouch

CVE-2025-49318: WPtouch: Cross-site scripting

WPtouch is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

PublishedJun 06, 2025
Safe version guidanceSee mitigation notes
Safe version
Jun 06, 2025 CVE-2025-49318
WPtouch: Cross-site scripting
WPtouch is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE5.9
NVDPending
Jan 09, 2023 CVE-2022-3417
WPtouch: Code execution
WPtouch is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
See mitigation notes
CVE8.8
NVD8.8
Jan 09, 2023 CVE-2022-3416
WPtouch: A security weakness
WPtouch is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE7.2
NVD7.2
Dec 14, 2011 CVE-2011-4803
WPTouch: SQL injection
WPTouch is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
See mitigation notes
CVE7.5
NVD7.5
Apr 07, 2011 CVE-2010-4779
Wptouch: Cross-site scripting
Wptouch is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE4.3
NVD4.3