dbcve.org
Contact FormWordPress extension · Bestwebsoft

CVE-2013-7481

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 3.3.5 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 contact-form-plugin plugin before 3.3.5 for WordPress has XSS.

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 contact-form-plugin for WordPress versions before 3.3.5 contains a Cross-Site Scripting (XSS) vulnerability. This allows attackers to inject malicious JavaScript code that executes in the browsers of users viewing affected pages, potentially stealing session cookies or performing actions on behalf of authenticated users.

MitigationUpdate the contact-form-plugin plugin to version 3.3.5 or later to patch the XSS vulnerability. Ensure backups are performed before updates and test the contact form functionality after updating.

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
Contact FormWordPress extension
Affected:< 3.3.5

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.0/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. Locate the plugin installation directory
    Check the WordPress plugins folder (wp-content/plugins/) for a folder named 'contact-form-plugin' or 'bestwebsoft-contact-form'
    Affected if The plugin folder exists in the WordPress installation
  2. Identify the installed version
    Open the main plugin PHP file (usually contact-form-plugin.php or similar) and look for the version comment header (e.g., 'Version: x.x.x')
    Affected if The version listed is lower than 3.3.5 (for example, 3.3.4, 3.3.0, etc.)
  3. Verify if the plugin is active
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and check if the Bestwebsoft Contact Form is activated
    Affected if The plugin shows as 'Active' in the WordPress admin plugins list
  4. Confirm the contact form is in use
    Check pages or posts where the contact form shortcode (typically [bestwebsoft_contact_form] or similar) has been added
    Affected if A contact form generated by this plugin is publicly accessible on the site

The environment is affected if the Bestwebsoft Contact Form plugin is installed, active, and the installed version is below 3.3.5.

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.

From vendor data
Upgrade available Upgrade to 3.3.5 or later
Fixed in 3.3.5
Interim mitigation

Update the contact-form-plugin plugin to version 3.3.5 or later to patch the XSS vulnerability. Ensure backups are performed before updates and test the contact form functionality after updating.

Fix this in Contact Form Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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