CVE-2025-60084
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 Elementor Forms + Drag And Drop Template Builder pdf-for-elementor-forms allows Object Injection.This issue affects PDF for Elementor 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 confidencePHP Object Injection vulnerability in the PDF for Elementor Forms plugin allows remote attackers to inject malicious PHP objects via unsafe deserialization of untrusted data. The vulnerability stems from the plugin's use of PHP unserialize() on user-controlled data without proper validation, potentially enabling code execution or other attacks depending on available PHP gadget chains.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Confirm the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'PDF for Elementor Forms' or check the plugins directory via file system at wp-content/plugins/Affected if The plugin is installed and active
-
Identify the installed versionCheck the plugin's main file (usually pdf-for-elementor-forms.php) for the 'Version' header in the plugin comment block, or look in the WordPress plugins admin panelAffected if Version matches the vulnerable range (compare against latest patched version once available)
-
Locate unsafe unserialize() callsSearch plugin PHP files for 'unserialize' using grep or a code editor: grep -r "unserialize" wp-content/plugins/pdf-for-elementor-forms/Affected if Found unserialize() calls that process untrusted input without prior validation
-
Check for data deserialization endpointsReview AJAX handlers, form processors, or any file that accepts POST/GET data and passes it to unserialize, especially files in includes/ or classes/ directoriesAffected if The plugin deserializes data from user input (form submissions, AJAX requests, or external sources)
-
Inspect plugin configurationCheck plugin settings pages for any options that store serialized data or enable third-party integrations that feed data into unserialize()Affected if Plugin is configured to accept or process external/unsanitized data
If the pdf-for-elementor-forms plugin is installed with a version that contains unserialize() calls processing 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 to the latest version of PDF for Elementor Forms + Drag And Drop Template Builder as soon as a patched release is available. Until then, consider disabling the plugin or restricting access to any forms functionality that processes serialized data.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60084 — 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-60084 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