CVE-2025-60080
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 add-ons.org PDF for Gravity Forms + Drag And Drop Template Builder pdf-for-gravity-forms allows Object Injection.This issue affects PDF for Gravity Forms + Drag And Drop Template Builder: from n/a through <= 6.5.0.
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 confidencePDF for Gravity Forms plugin <= 6.5.0 is vulnerable to PHP object injection via unsafe deserialization of untrusted data. This allows attackers to potentially instantiate malicious PHP objects, which if suitable gadget chains exist in the application or loaded libraries, could lead to remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 the PDF for Gravity Forms pluginCheck your WordPress plugins directory for a folder containing 'pdf-for-gravity-forms' or search for files with 'GravityView' or PDF-related classes in the wp-content/plugins directoryAffected if The plugin folder exists on the server
-
Identify the installed versionCheck the main plugin file (usually index.php or the primary PHP file in the plugin folder) for a 'Version:' comment in the file header, or look for a version defined in the plugin's main PHP fileAffected if The reported version is 6.5.0 or lower
-
Verify the plugin is activeQuery the WordPress database 'wp_options' table for the option 'active_plugins' or use the WordPress admin to check if PDF for Gravity Forms appears in the list of active pluginsAffected if The plugin appears in the active plugins list
-
Inspect for unserialize() callsSearch the plugin's PHP files for instances of 'unserialize()' function calls, particularly those processing data from user input (POST, GET, cookie, or request parameters)Affected if The plugin contains unserialize() calls handling untrusted input
-
Check for suspicious filesReview the wp-content/uploads and wp-content/plugins directories for newly created PHP files with obfuscated code or files modified after the last legitimate updateAffected if Unexpected PHP files exist in these directories
If PDF for Gravity Forms plugin version 6.5.0 or lower is installed and active with unserialize() handling untrusted input, the environment is vulnerable to PHP object injection.
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 plugin to the latest patched version (beyond 6.5.0) immediately. Until a patch is available, disable the plugin and review for any suspicious activity.
- 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-2025-60080 — 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-2025-60080 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