dbcve.org
Header Footer Code ManagerWordPress extension · Draftpress

CVE-2022-0710

MEDIUM · 6.1 CVSS v3.1 Published 2022-02-24
Fix available
A fix is available. Upgrade to after 1.1.16 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The Header Footer Code Manager plugin <= 1.1.16 for WordPress is vulnerable to Reflected Cross-Site Scripting (XSS) via the $_REQUEST['page'] parameter.

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 confidence

The Header Footer Code Manager plugin for WordPress versions 1.1.16 and below is vulnerable to reflected cross-site scripting (XSS). The vulnerability stems from improper sanitization of the $_REQUEST['page'] parameter, allowing attackers to inject malicious JavaScript through crafted URLs that execute in victim browsers.

MitigationUpgrade to version 1.1.17 or later, which contains the security fix. Alternatively, implement proper input validation and output encoding on the 'page' parameter before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Header Footer Code ManagerWordPress extension
Affected:<= 1.1.16

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Header Footer Code Manager plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Header Footer Code Manager' by Draftpress. Alternatively, check the /wp-content/plugins/ directory for the header-footer-code-manager folder.
    Affected if The plugin folder 'header-footer-code-manager' exists in the WordPress plugins directory
  2. Determine the installed version of the plugin
    In WordPress admin, find the plugin in the Plugins list and look at the version number displayed below the plugin name. Or read the main plugin file (usually header-footer-code-manager.php) and look for the 'Version' header in the plugin comments. You can also use WP-CLI: wp plugin list --filter=name=header-footer-code-manager --format=json
    Affected if The version listed is 1.1.16 or any version number lower than 1.1.16
  3. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm the 'Header Footer Code Manager' plugin has the 'Active' status. Alternatively, query the wp_options table for option_name = 'active_plugins' and check if the plugin is in the active list.
    Affected if The plugin is installed and activated in WordPress, making the vulnerable code accessible
  4. Confirm the vulnerability condition
    The reflected XSS occurs when the $_REQUEST['page'] parameter is not properly sanitized before output. This affects admin pages that handle the 'page' parameter in the plugin. If you are on version 1.1.16 or below and the plugin is active, the vulnerable code path exists.
    Affected if You are running version 1.1.16 or lower AND the plugin is active, meaning the vulnerable code that improperly handles the 'page' parameter is present and accessible

You are affected if the Header Footer Code Manager plugin by Draftpress is installed at version 1.1.16 or lower and is currently activated on your WordPress site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.1.16
Interim mitigation

Upgrade to version 1.1.17 or later, which contains the security fix. Alternatively, implement proper input validation and output encoding on the 'page' parameter before rendering.

Recommended fix Moderate confidence

1.1.17 or later

  1. Upgrade the Header Footer Code Manager plugin to version 1.1.17 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Header Footer Code Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0710 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-0710 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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