GravityformsWordPress extension · Rocketgenius
CVE-2020-27851
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 · uneditedMultiple stored HTML injection vulnerabilities in the "poll" and "quiz" features in an additional paid add-on of Rocketgenius Gravity Forms before 2.4.21 allows remote attackers to inject arbitrary HTML code via poll or quiz answers. This code is interpreted by users in a privileged role (Administrator, Editor, etc.).
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 confidenceStored HTML injection (XSS) vulnerability in the Gravity Forms paid add-on's poll and quiz features allows remote attackers to inject arbitrary HTML/JS via poll or quiz answer fields. The malicious payload persists in the database and executes when viewed by privileged users (Administrator, Editor).
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
GravityformsWordPress extension
< 2.4.21CVSS 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.
-
Identify Gravity Forms versionAccess WordPress admin panel, navigate to Forms > Settings, or check the plugins directory to determine the installed version of the Gravity Forms pluginAffected if The installed version is lower than 2.4.21
-
Confirm paid add-on installationCheck if the Gravity Forms paid add-on (containing poll and quiz features) is installed and active in the WordPress plugins sectionAffected if The poll and quiz add-on is installed and active in any version below 2.4.21
-
Locate poll and quiz form entriesReview your WordPress database tables containing form entries, specifically look for entries created using forms with poll or quiz fields enabledAffected if Poll or quiz forms exist and contain user-submitted answer data in the database
-
Inspect stored answer data for malicious contentExamine the database records for poll and quiz answer fields, looking for unusual HTML tags, script elements, or javascript: URIs that could indicate injected payloadsAffected if Any poll or quiz answer entries contain unsanitized HTML or JavaScript code such as <script> tags, event handlers, or iframe elements
You are affected if you have Gravity Forms paid add-on with poll/quiz features enabled below version 2.4.21 and have any stored entries containing suspicious HTML or script content in those fields.
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 data2.4.21
Upgrade the Gravity Forms paid add-on to version 2.4.21 or later to patch the stored XSS vulnerability in the poll and quiz features.
Fix this in Gravityforms
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27851 — 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-2020-27851 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