Zoho FormsWordPress extension · Zohocorp
CVE-2023-50891
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Zoho Forms Form plugin for WordPress – Zoho Forms allows Stored XSS.This issue affects Form plugin for WordPress – Zoho Forms: from n/a through 3.0.1.
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 confidenceThis is a stored Cross-site Scripting (XSS) vulnerability in the Zoho Forms WordPress plugin (versions through 3.0.1). The plugin fails to properly sanitize user input during form submission, allowing malicious scripts to be persisted and executed when other users view the affected pages in the WordPress admin or frontend.
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
Zoho FormsWordPress extension
<= 3.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Zoho Forms plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the 'zoho-forms' folder, or list installed plugins via wp-cli: wp plugin list --status=active --field=nameAffected if The plugin folder 'zoho-forms' exists in the plugins directory or appears in the active plugins list
-
Identify the installed versionRead the main plugin file header in wp-content/plugins/zoho-forms/zoho-forms.php, look for 'Version:' comment, or run: wp plugin get zoho-forms --field=versionAffected if The version number is 3.0.1 or lower (the vulnerable range is <= 3.0.1)
-
Verify form submissions existCheck the WordPress database for entries in tables related to Zoho Forms submissions (typically wp_zf_form_entries or similar), or inspect form entries through the WordPress admin under Zoho Forms > EntriesAffected if Any form submissions exist in the database - the XSS payload would be stored in submission data
-
Inspect stored form data for malicious contentExamine form entry records in the database for unsanitized script tags or HTML in input fields, or view submitted entries through the admin interface and inspect page source for unescaped HTMLAffected if Form entries contain raw HTML or script tags that render in the browser without encoding
A user is affected if the Zoho Forms plugin version is 3.0.1 or lower AND form submissions containing malicious scripts have been stored in the database.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the Zoho Forms plugin to the latest version available from WordPress repository, or apply vendor-provided patch that implements proper input validation and output encoding for all form fields.
Fix this in Zoho Forms
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50891 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-50891 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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