Vulnerabilities

Vulnerability · CVE-2026-3516

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.

Published Mar 21, 2026 · catalog updated Jun 17, 2026 · The Contact List plugin

Check if you run it

No confirmed exploitation is on record for CVE-2026-3516. EPSS is 0.37%. Act only if a listed version of The Contact List plugin is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The Contact List plugin).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.37%
Remediation
Version ranges on file
Affected products
stated named in the record

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 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • stated named in the record<= 3.0.18

How to fix CVE-2026-3516

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-3516. EPSS is 0.37%. Act only if a listed version of The Contact List plugin is installed.

Which versions are affected?

Compare what you have installed with named in the record <= 3.0.18. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-79: Cross-site Scripting (XSS). EPSS 0.37%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 21, 2026 · NIST NVD

    Detected

    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 tags from user input b

  2. Jun 17, 2026 · NIST NVD

    Updated

    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 tags from user input b

Sources

  • CVE.orgVulnerability recordCVE-2026-3516

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-3516

    30-day exploitation probability 0.4%

    first.org
  • NIST NVDVulnerability recordCVE-2026-3516

    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

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.