dbcve.org
Redirection For Contact Form 7WordPress extension · Redirection For Contact Form7

CVE-2021-36913

HIGH · 7.5 CVSS v3.1 Published 2022-10-11
Fix available
A fix is available. Upgrade to 2.6.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Unauthenticated Options Change and Content Injection vulnerability in Qube One Redirection for Contact Form 7 plugin <= 2.4.0 at WordPress allows attackers to change options and inject scripts into the footer HTML. Requires an additional extension (plugin) AccessiBe.

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 Qube One Redirection for Contact Form 7 plugin <= 2.4.0 has an unauthenticated options change vulnerability allowing attackers to modify plugin settings without authentication, combined with a stored XSS vulnerability enabling script injection into footer HTML. The attack requires the AccessiBe extension plugin to be installed.

MitigationUpdate the Qube One Redirection for Contact Form 7 plugin to the latest patched version. If no patch is available, disable and remove the plugin, and review WordPress for any unauthorized script injections in the database and footer areas.

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
Redirection For Contact Form 7WordPress extension
Affected:< 2.6.0

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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Verify Qube One Redirection for Contact Form 7 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Qube One Redirection for Contact Form 7' or 'Redirection For Contact Form7'. Alternatively, check the wp-content/plugins/ directory for folders containing 'qube' or 'redirection-for-contact-form-7'.
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, click on the plugin from the Plugins list and view the version number displayed. Alternatively, open the main plugin PHP file (usually qube-one-redirection-for-contact-form-7.php or similar) and look for the Version header in the plugin comments.
    Affected if The version number is less than 2.6.0 or cannot be determined (implies vulnerable)
  3. Verify if AccessiBe extension plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'AccessiBe' or 'Accessibe' extension plugin. Check wp-content/plugins/ for folders containing 'accessibe'.
    Affected if The AccessiBe extension plugin is present alongside the Qube One Redirection plugin
  4. Inspect plugin settings for unauthorized changes
    Navigate to the plugin settings page in WordPress admin (usually under Contact > CF7 Redirection or Settings > Qube One). Review all configuration options for unexpected values, especially settings related to footer HTML, scripts, or external redirects.
    Affected if Settings have been modified without administrator action or contain suspicious script/redirect values
  5. Check footer HTML and database for injected scripts
    View the website frontend source code (right-click > View Page Source) and search for any unfamiliar JavaScript tags in the <footer> area. Also review wp_options table in the database for any rows with option_names containing 'qube' or 'cf7_redirection' with unexpected script content.
    Affected if Unknown script tags appear in the footer or suspicious entries exist in the database options table

The environment is affected if the Qube One Redirection for Contact Form 7 plugin is installed with a version below 2.6.0 AND the AccessiBe extension plugin is also present.

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 2.6.0 or later
Fixed in 2.6.0
Interim mitigation

Update the Qube One Redirection for Contact Form 7 plugin to the latest patched version. If no patch is available, disable and remove the plugin, and review WordPress for any unauthorized script injections in the database and footer areas.

Recommended fix High confidence

2.6.0

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Redirection For Contact Form 7'
  4. Check if the current version is less than 2.6.0
  5. If vulnerable, click 'Update Now' to update to the latest version (2.6.0 or higher)
  6. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the plugin version is 2.6.0 or newer

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

Fix this in Redirection For Contact Form 7 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-36913 — 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-2021-36913 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