Gravity FormsWordPress extension · Gravityforms
CVE-2023-28782
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 · uneditedDeserialization of Untrusted Data vulnerability in Rocketgenius Inc. Gravity Forms.This issue affects Gravity Forms: from n/a through 2.7.3.
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 · moderate confidenceA deserialization of untrusted data vulnerability in Gravity Forms (versions through 2.7.3) allows attackers to potentially execute arbitrary code by supplying malicious serialized data that gets processed without proper validation. This type of vulnerability is critical because deserialization flaws can lead to remote code execution.
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
Gravity FormsWordPress extension
< 2.7.4CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate installed Gravity Forms versionIn WordPress admin, go to Plugins > Installed Plugins > find Gravity Forms and read the version number. Alternatively, check the plugin main file (wp-content/plugins/gravityforms Gravity Forms/gravityforms.php) for the 'Version' header comment, or run: wp plugin list --name='gravityforms' --format=jsonAffected if version displayed is 2.7.3 or lower, or if no version is shown but the plugin file exists with a version header below 2.7.4
-
Confirm plugin is activeIn WordPress admin under Plugins > Installed Plugins, verify that Gravity Forms shows as 'Active' (not 'Inactive' or 'Must-Use'). Alternatively, run: wp plugin is-active gravityformsAffected if plugin status is Active - only active plugins process deserialized data and are vulnerable to this flaw
-
Check for recent plugin file modificationsReview file modification timestamps on gravityforms plugin directory (wp-content/plugins/gravityforms Gravity Forms/) using FTP, SSH (ls -la), or file manager. Compare against expected baseline or known-good state.Affected if plugin files show unexpected recent modifications that were not made by your own updates - may indicate exploitation attempts
You are affected if Gravity Forms version is below 2.7.4 AND the plugin is currently active in your WordPress installation.
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.
dbcve · scoped2.7.4
Update Gravity Forms to the latest patched version immediately. If immediate updating is not feasible, restrict access to the plugin admin interfaces and monitor for indicators of compromise, while planning for urgent patching.
2.7.4
- Upgrade Gravity Forms to version 2.7.4 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Gravity Forms
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-2023-28782 — 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-28782 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