GravityformsWordPress extension · Rocketgenius
CVE-2020-13764
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 · uneditedcommon.php in the Gravity Forms plugin before 2.4.9 for WordPress can leak hashed passwords because user_pass is not considered a special case for a $current_user->get($property) call.
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 confidenceThe Gravity Forms plugin before version 2.4.9 has an information disclosure vulnerability in common.php where the $current_user->get($property) method does not properly filter the 'user_pass' field. This causes hashed passwords to be returned and potentially exposed when the method is called, allowing attackers to obtain password hashes.
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.9CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 plugin versionNavigate to WordPress admin > Plugins > Installed Plugins > Gravity Forms and check the 'Version' field displayed there, or check the version in the plugin's main PHP file headerAffected if The installed version number is lower than 2.4.9 (e.g., 2.4.8, 2.4.7, 2.4.6, etc.)
-
Locate the vulnerable common.php fileIn the WordPress wp-content/plugins/gravityforms directory, locate the common.php file and inspect the $current_user->get() method calls, specifically looking for code that retrieves user properties without filtering sensitive fieldsAffected if The common.php file exists in the Gravity Forms plugin directory and contains $current_user->get($property) calls that do not explicitly exclude the 'user_pass' field
-
Verify user data exposure potentialCheck if the WordPress user data retrieval is accessible through Gravity Forms functionality - test any feature that calls or outputs user data via the vulnerable method (such as user profile display hooks, form user fields, or admin user listing integrations)Affected if The application allows any user-facing or admin-facing feature that could invoke $current_user->get('user_pass') and return the hashed password value
You are affected if the Gravity Forms plugin version is below 2.4.9 and the vulnerable code in common.php is present and accessible in your environment.
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.9
Update the Gravity Forms plugin to version 2.4.9 or later to remediate this vulnerability. Verify that user authentication and form functionality remain intact after the update.
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-13764 — 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-13764 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