dbcve.org
Html FormsWordPress extension · Linksoftwarellc

CVE-2025-46236

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to 1.5.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Link Software LLC HTML Forms html-forms allows Stored XSS.This issue affects HTML Forms: from n/a through <= 1.5.2.

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

A stored cross-site scripting (XSS) vulnerability exists in the HTML Forms plugin where user-supplied input is not properly sanitized before being rendered in web pages. An attacker with the ability to submit forms can inject malicious JavaScript code that will execute in the browsers of other users who view the affected pages.

MitigationImplement proper input validation and output encoding/escaping for all user-supplied data before rendering it in HTML contexts. Consider using a security-focused templating library or existing XSS prevention functions.

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
Html FormsWordPress extension
Affected:< 1.5.3

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm HTML Forms plugin is installed
    Locate and verify the Linksoftwarellc Html Forms plugin in your system's plugin/component list. Check the plugin directory or admin interface where third-party extensions are listed.
    Affected if The plugin is present and enabled in the environment
  2. Determine installed version of HTML Forms
    Check the plugin's version metadata. This is typically found in the plugin's main file, version manifest, or admin interface under plugin details. Compare the version number to the affected range.
    Affected if The installed version is lower than 1.5.3
  3. Verify public form submission is enabled
    Examine the HTML Forms plugin configuration settings. Look for options that control whether anonymous or unauthenticated users can submit forms. Check for any public-facing form settings.
    Affected if Public form submissions are allowed and the plugin handles form data display
  4. Inspect form field configurations for input handling
    Review the form definitions created with HTML Forms. Identify which form fields accept free-text input that could contain scriptable content. Check if any fields are configured to display submitted data without encoding.
    Affected if Forms contain text input fields that display submitted content to other users

You are affected if Linksoftwarellc Html Forms is installed with a version lower than 1.5.3 and public form submissions are enabled, allowing users to submit content that gets displayed to others without sanitization.

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.5.3 or later
Fixed in 1.5.3
Interim mitigation

Implement proper input validation and output encoding/escaping for all user-supplied data before rendering it in HTML contexts. Consider using a security-focused templating library or existing XSS prevention functions.

Recommended fix High confidence

1.5.3

  1. 1. Backup your current website and database before making any changes
  2. 2. Navigate to your WordPress admin dashboard or the plugin management interface
  3. 3. Locate the HTML Forms plugin in your plugins list
  4. 4. Update the plugin to version 1.5.3 or later
  5. 5. Verify the update was successful by checking the plugin version
  6. 6. Test form functionality to ensure the XSS vulnerability is remediated

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

Fix this in Html Forms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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