CVE-2026-3516 json
Contact List <= 3.0.18 - Authenticated (Contributor+) Stored Cross-Site Scripting via '_cl_map_iframe' Parameter
published 7mo ago modified 4mo ago also EUVD-2026-13922
- cvss
- 6.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
The Contact List plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '_cl_map_iframe' parameter in all versions up to, and including, 3.0.18. This is due to insufficient input sanitization and output escaping when handling the Google Maps iframe custom field. The saveCustomFields() function in class-contact-list-custom-fields.php uses a regex to extract <iframe> tags from user input but does not validate or sanitize the iframe's attributes, allowing event handlers like 'onload' to be included. The extracted iframe HTML is stored via update_post_meta() and later rendered on the front-end in class-cl-public-card.php without any escaping or wp_kses filtering. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Is CVE-2026-3516 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
Affected products
- anssilaitila Contact List – Online Staff Directory & Address Book
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/a8059995-55cb-49ee-add1-f5364d0772eb?source=cve
- plugins.trac.wordpress.org /browser/contact-list/trunk/public/class-cl-public-card.php#L466
- plugins.trac.wordpress.org /browser/contact-list/tags/3.0.17/public/class-cl-public-card.php#L466
- plugins.trac.wordpress.org /browser/contact-list/trunk/includes/class-contact-list-custom-fields.php#L697
- plugins.trac.wordpress.org /browser/contact-list/tags/3.0.17/includes/class-contact-list-custom-fields.php#L697
- plugins.trac.wordpress.org /browser/contact-list/trunk/includes/class-contact-list-custom-fields.php#L675
- plugins.trac.wordpress.org /browser/contact-list/tags/3.0.17/includes/class-contact-list-custom-fields.php#L675
- plugins.trac.wordpress.org /changeset/3486445
Sources
- CVE List CVE-2026-3516
- NVD CVE-2026-3516
Fencer Intel 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.