dbcve.org
Form MakerWordPress extension · 10web

CVE-2023-45070

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-18
Fix available
A fix is available. Upgrade to 1.15.19 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
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in 10Web Form Builder Team Form Maker by 10Web – Mobile-Friendly Drag & Drop Contact Form Builder plugin <= 1.15.18 versions.

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

An unauthenticated reflected Cross-Site Scripting (XSS) vulnerability exists in the Form Maker by 10Web WordPress plugin versions 1.15.18 and below. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that gets reflected back in the HTTP response without proper output encoding.

MitigationUpdate the Form Maker by 10Web plugin to a version newer than 1.15.18. If immediate patching is not possible, disable the plugin until an update can be applied.

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
Form MakerWordPress extension
Affected:< 1.15.19

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. Locate the Form Maker plugin installation directory
    Check the WordPress plugins folder at wp-content/plugins/form-maker for the presence of the plugin files
    Affected if The plugin directory does not exist - the plugin is not installed and is not vulnerable
  2. Determine the installed plugin version
    Open the main plugin file (usually form-maker.php) and locate the version header comment, or check the WordPress admin under Plugins > Installed Plugins
    Affected if The version found is 1.15.18 or lower (any version below 1.15.19)
  3. Verify the plugin is active
    Check WordPress admin under Plugins > Installed Plugins to confirm Form Maker by 10Web shows as Active, or query the wp_options table for option_name 'active_plugins'
    Affected if The plugin is active - only active installations can be exploited through the reflected XSS
  4. Confirm the vulnerability is exploitable via frontend
    This is a reflected XSS requiring no authentication; check if the plugin's form submission or preview functionality is publicly accessible (no login required)
    Affected if The form maker frontend endpoints are publicly accessible without authentication

The environment is affected if Form Maker by 10Web is installed, active, and running version 1.15.18 or below.

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

Update the Form Maker by 10Web plugin to a version newer than 1.15.18. If immediate patching is not possible, disable the plugin until an update can be applied.

Recommended fix High confidence

1.15.19

  1. Create a full backup of your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find 'Form Maker by 10Web' in the plugin list
  4. Click 'Update now' on the plugin to update to version 1.15.19, or manually download version 1.15.19 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the plugin version shows 1.15.19 or higher in the plugins list
  6. Clear any caching plugins and server-side caches to ensure the patched version is served

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

Fix this in Form Maker Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.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-2023-45070 — 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-2023-45070 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