CVE-2026-6696 json
Zingaya Click-to-Call <= 1.0 - Reflected Cross-Site Scripting via 'email' Parameter
published 2026-05-05 6 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-27201
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
The Zingaya Click-to-Call plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'email', 'first_name', 'last_name', and 'phone' parameters on the plugin's sign-up admin page in all versions up to, and including, 1.0. This is 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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- zingaya Zingaya Click-to-Call
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/5bdd515c-6b52-467c-9446-6ae9b3b75e50?source=cve
- wordpress.org /plugins/zingaya-click-to-call/
- plugins.trac.wordpress.org /browser/zingaya-click-to-call/tags/1.0/zingaya-admin.php#L62
- plugins.trac.wordpress.org /browser/zingaya-click-to-call/tags/1.0/zingaya-admin.php#L71
- plugins.trac.wordpress.org /browser/zingaya-click-to-call/tags/1.0/zingaya-admin.php#L79
- plugins.trac.wordpress.org /browser/zingaya-click-to-call/tags/1.0/zingaya-admin.php#L104
Sources
- CVE List CVE-2026-6696
- NVD CVE-2026-6696
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.