Vulnerabilities

Vulnerability · CVE-2026-2305

The AddFunc Head & Footer Code plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the , , and post meta values in all versions up to, and including,…

Published Apr 10, 2026 · catalog updated Jun 17, 2026 · the affected product

Check if you run it

No confirmed exploitation is on record for CVE-2026-2305. EPSS is 0.20%. Act only if a listed version of the affected product is installed.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • 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.20%
Remediation
Version ranges on file
Affected products
stated named in the record

The AddFunc Head & Footer Code plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the , , and post meta values in all versions up to, and including, 2.3. This is due to the plugin outputting these meta values without any sanitization or escaping. While the plugin restricts its own metabox and save handler to administrators via , it does not use with an to protect these meta keys. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts via the WordPress Custom Fields interface that execute when an administrator previews or views the post.

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<= 2.3

How to fix CVE-2026-2305

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-2305. EPSS is 0.20%. Act only if a listed version of the affected product is installed.

Which versions are affected?

Compare what you have installed with named in the record <= 2.3. 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.20%. 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. Apr 10, 2026 · NIST NVD

    Detected

    The AddFunc Head & Footer Code plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the , , and post meta values in all versions up to, and including, 2.3. This is due to the plugin outputting these meta values without any sanitization or escaping. While the plugin restricts its own metabox and save handler to administrators via , it does not use with an to protect these meta keys

  2. Jun 17, 2026 · NIST NVD

    Updated

    The AddFunc Head & Footer Code plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the , , and post meta values in all versions up to, and including, 2.3. This is due to the plugin outputting these meta values without any sanitization or escaping. While the plugin restricts its own metabox and save handler to administrators via , it does not use with an to protect these meta keys

Sources

  • CVE.orgVulnerability recordCVE-2026-2305

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-2305

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-2026-2305

    The AddFunc Head & Footer Code plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the , , and post meta values in all versions up to, and including, 2.3. This is due to the plugin outputting these meta value

    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.