dbcve.org
Form MakerWordPress extension · 10web

CVE-2023-45071

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. Stored 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 stored Cross-Site Scripting (XSS) vulnerability exists in the Form Maker by 10Web WordPress plugin (versions <= 1.15.18). Attackers can inject malicious JavaScript code through form submission fields, which gets stored in the database and executes when administrators or other users view the submitted form data in the plugin's dashboard.

MitigationUpdate the Form Maker plugin to a version newer than 1.15.18. If an update is unavailable, disable the plugin until a patched version is released, as the unauthenticated stored XSS can lead to session hijacking and administrative account compromise.

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. Verify Form Maker plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Form Maker by 10Web' in the list of installed plugins.
    Affected if The Form Maker by 10Web plugin appears in the installed plugins list.
  2. Check installed version number
    In the Plugins list, locate Form Maker by 10Web and note the version number displayed under the plugin name. Compare this version to the affected range: any version below 1.15.19 is vulnerable.
    Affected if The installed version is 1.15.18 or lower.
  3. Verify plugin is active
    In WordPress admin > Plugins, check if Form Maker by 10Web shows as 'Active'. The vulnerability requires the plugin to be enabled to accept malicious form submissions.
    Affected if The plugin status shows as Active.
  4. Inspect database for stored form submissions
    Access the WordPress database via phpMyAdmin or command line. Query the plugin's form submission tables (typically wp_formmaker_submits or similar, depending on table prefix) for any submissions containing script tags, javascript: URIs, or HTML event attributes.
    Affected if Form submission records contain unsanitized script tags or event handlers (onerror, onload, onclick, etc.).

If the Form Maker by 10Web plugin is installed, active, and running version 1.15.18 or lower, the environment is affected by this stored XSS vulnerability.

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 plugin to a version newer than 1.15.18. If an update is unavailable, disable the plugin until a patched version is released, as the unauthenticated stored XSS can lead to session hijacking and administrative account compromise.

Recommended fix High confidence

1.15.19

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Form Maker plugin (by 10Web)
  4. Check the current version - if it is 1.15.18 or lower, an update is needed
  5. Click 'Update Now' when update to version 1.15.19 is available, or manually download version 1.15.19 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin shows version 1.15.19

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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