dbcve.org
Advanced Cf7 DbWordPress extension · Vsourz

CVE-2022-29408

MEDIUM · 6.1 CVSS v3.1 Published 2022-05-25
Fix available
A fix is available. Upgrade to after 1.8.7 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
Persistent Cross-Site Scripting (XSS) vulnerability in Vsourz Digital's Advanced Contact form 7 DB plugin <= 1.8.7 at WordPress.

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 · moderate confidence

A persistent Cross-Site Scripting (XSS) vulnerability exists in Vsourz Digital's Advanced Contact Form 7 DB plugin for WordPress versions 1.8.7 and below. The vulnerability allows malicious JavaScript to be stored in the database via form submissions and executed when other users or administrators view the stored data in the plugin's admin interface.

MitigationUpdate the Advanced Contact Form 7 DB plugin to a version higher than 1.8.7. If an update is unavailable, consider removing or replacing the plugin. Implement input sanitization and output encoding on any custom code handling form data.

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
Advanced Cf7 DbWordPress extension
Affected:<= 1.8.7

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. Identify plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Advanced Contact Form 7 DB. The version number is displayed below the plugin name. Alternatively, inspect the plugin header in /wp-content/plugins/advanced-contact-form-7-db/readme.txt or the main plugin PHP file.
    Affected if The installed version is 1.8.7 or lower.
  2. Verify plugin is active
    In WordPress admin, check if Advanced Contact Form 7 DB appears in the list of active plugins. The vulnerability only applies when the plugin is actively storing form submissions.
    Affected if The plugin is installed and active, storing form data.
  3. Inspect database submission tables
    Access the WordPress database (via phpMyAdmin or command line). Locate the table that stores Cf7 form submissions, typically named wp_advanced_cf7_db or similar. Query for entries containing HTML script tags, javascript: URLs, or onload/onerror attributes.
    Affected if Any form submission entries contain unencoded HTML or JavaScript code, indicating stored XSS payloads exist.
  4. Review admin access logs
    Check WordPress activity logs or server access logs for entries where admin users accessed the plugin's submission viewing interface (typically under the Cf7 DB menu in WordPress admin).
    Affected if Admins have accessed the submission viewer after external form submissions were received, which would have triggered any stored XSS payloads.

You are affected if the Advanced Contact Form 7 DB plugin version is 1.8.7 or lower, the plugin is active and storing form data, and any form submissions contain unescaped HTML or JavaScript that could execute when viewed in the admin interface.

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.8.7
Interim mitigation

Update the Advanced Contact Form 7 DB plugin to a version higher than 1.8.7. If an update is unavailable, consider removing or replacing the plugin. Implement input sanitization and output encoding on any custom code handling form data.

Recommended fix Moderate confidence

Version 1.8.8 or later (upgrade to the latest available version of the plugin)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Advanced Cf7 Db' or 'Advanced Contact form 7 DB' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running version 1.8.8 or higher
  6. 6. Test contact form submissions to ensure the plugin functions correctly after the update
Caveat Review plugin changelog for any functional changes between 1.8.7 and the new version

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

Fix this in Advanced Cf7 Db Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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