VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

Contact Form DB <= 2.8.17 — Reflected Cross-Site Scripting

a06812c5-43db-4c32-a9fb-f7b86900a741Published · Updated

Action summary

Affected: <2.8.18Update to 2.8.18 or newer

All remediation steps
Watch plugin
Severity
Medium6.1
CVSS
6.1
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:R User interaction
Required
S:C Scope
Changed
C:L Confidentiality
Low
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-79 Cross-Site Scripting
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

Contact Form DB contact-form-7-to-database-extension

  1. Affected< 2.8.18
  2. Patched in2.8.18

Update to 2.8.18 or newer.

You are affected if you run < 2.8.18. Version 2.8.18 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Contact Form DB.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.8.18, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Contact Form DB to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Tim Coen.

The Contact Form DB plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'submit_time' and 'form_name' parameters in versions up to, and including, 2.8.17 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Contact Form DB

All 5
More vulnerabilities in Contact Form DB
SeverityVulnerabilityCVEPublished
High8.6CSV Injection
2.10.32 – 2.10.32Update to 2.10.36
CVE-2018-9035
Medium4.3Cross-site request forgery via a request in the CF7DBPluginSubmissions page to wp-admin/admin.php
≤2.8.29Update to 2.8.32
CVE-2015-1874
Medium6.5Authenticated Cross-Site Scripting
≤2.8.26Update to 2.8.28
CVE-2015-2040
Medium6.1Cross-Site Scripting
≤2.8.19Update to 2.8.20
CVE-2014-7139

Same weakness (Cross-Site Scripting)

All Cross-Site Scripting
Other Cross-Site Scripting vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent Header
EZ SQL Reports Shortcode Widget and DB Backup≤5.25.25Update to 5.26.45
CVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form Submission
Chatterbug Forms – Fast, Flexible WordPress Form Builder≤1.0.2Update to 1.1
CVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' Parameter
ELEX WordPress HelpDesk & Customer Ticketing System≤3.3.9Update to 3.4.0
CVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 6.1

  2. Record last updated

Sources & licenses

Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?