CVE-2026-2305
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe AddFunc Head & Footer Code plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `aFhfc_head_code`, `aFhfc_body_code`, and `aFhfc_footer_code` 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 `current_user_can('manage_options')`, it does not use `register_meta()` with an `auth_callback` 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe AddFunc Head & Footer Code plugin for WordPress fails to protect its post meta keys (`aFhfc_head_code`, `aFhfc_body_code`, `aFhfc_footer_code`) using `register_meta()` with an `auth_callback`. While the plugin's own admin UI restricts access to administrators, WordPress's Custom Fields interface allows any authenticated user with Contributor-level access or higher to modify these meta values. When administrators preview or view posts containing injected scripts, the unsanitized meta values execute as arbitrary JavaScript.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'AddFunc Head & Footer Code' or search for the plugin files in /wp-content/plugins/ directoryAffected if The plugin is installed and active
-
Check plugin versionIn the plugins list, note the version number displayed under the plugin name. Compare against any known affected versions.Affected if Version is within an affected range (no specific range provided; assume all versions could be affected)
-
Identify meta keys in databaseQuery the wp_postmeta table for meta keys: aFhfc_head_code, aFhfc_body_code, aFhfc_footer_code using: SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE meta_key IN ('aFhfc_head_code', 'aFhfc_body_code', 'aFhfc_footer_code')Affected if These meta keys exist in the database with non-empty values
-
Check for unauthorized meta modificationsReview the meta values found for any suspicious JavaScript tags (<script>, javascript:, onload, onerror) or unfamiliar third-party tracking codeAffected if Meta values contain unescaped HTML, script tags, or JavaScript event handlers
-
Verify user role access to Custom FieldsNavigate to a post editor as a Contributor or Author role user. If the Custom Fields metabox (or Custom Fields panel in block editor) is visible and accessible, the vulnerability is exploitable.Affected if Non-administrator users can access and modify the Custom Fields interface
If the AddFunc Head & Footer Code plugin is installed, any user with Contributor-level access can inject malicious code via Custom Fields that executes when administrators view the affected posts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedThe plugin developer should implement `register_meta()` with a proper `auth_callback` to restrict meta key modifications to administrators, or add output sanitization/escaping when rendering the stored code values. Until an official patch is released, restrict user access to the Custom Fields interface via role management or disable the interface for non-administrators.
Version 2.4 or latest available release (replace version 2.3)
- 1. Log in to the WordPress admin dashboard with administrator privileges.
- 2. Navigate to Plugins > Installed Plugins.
- 3. Locate the 'AddFunc Head & Footer Code' plugin in the plugin list.
- 4. If an update is available, click 'Update Now' to install the latest version.
- 5. After updating, verify the plugin is running version 2.4 or higher.
- 6. Confirm the update was successful by checking the plugin version on the Plugins page.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2305 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2305 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data