dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-60082

HIGH · 8.8 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Deserialization of Untrusted Data vulnerability in add-ons.org PDF for WPForms pdf-for-wpforms allows Object Injection.This issue affects PDF for WPForms: 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 confidence

This is a PHP Object Injection vulnerability in the PDF for WPForms WordPress plugin. The plugin deserializes untrusted data (likely via PHP's unsafe unserialize() function), allowing authenticated attackers to inject malicious PHP objects. Successful exploitation can lead to remote code execution, file operations, or SQL injection by leveraging available gadget chains in WordPress or other plugins.

MitigationUpdate PDF for WPForms to the latest version once a patch is released. Until then, restrict plugin access to trusted users only and consider deploying a WAF rule to block serialized data patterns in HTTP requests.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify PDF for WPForms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PDF for WPForms' or check the /wp-content/plugins/ directory for the pdf-for-wpforms folder. Also check if the plugin is active.
    Affected if The plugin is installed and active, indicating the vulnerable code is present in the environment.
  2. Identify the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on the plugin name to view details and note the version number. Alternatively, check the main plugin file (e.g., pdf-for-wpforms.php) for the 'Version' header in the plugin comments.
    Affected if The installed version falls within the range that contains the unsafe deserialization vulnerability.
  3. Confirm the vulnerable deserialization code exists
    Search the plugin files for patterns like 'unserialize($_POST', 'unserialize($_GET', or 'unserialize($_REQUEST' using a file search or grep tool within the plugin directory.
    Affected if The plugin contains unserialize() calls that process untrusted input without validation, which is the core vulnerability.
  4. Check for user accounts with plugin access
    Review WordPress user roles and capabilities. Go to Users > All Users and identify accounts with access to WPForms functionality or plugin settings where the deserialization occurs.
    Affected if Any authenticated user (subscriber or higher) can trigger the vulnerable code path, making the vulnerability exploitable.
  5. Inspect HTTP request patterns
    Review web server access logs or WAF logs for incoming requests containing PHP serialized data patterns (e.g., 'O:', 'a:', 's:') in query parameters, POST bodies, or cookies that target the plugin endpoints.
    Affected if Such patterns indicate potential exploitation attempts or presence of the vulnerable data injection point.

You are affected if the PDF for WPForms plugin is installed with a version containing the unsafe unserialize() vulnerability and any authenticated user can access the plugin functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update PDF for WPForms to the latest version once a patch is released. Until then, restrict plugin access to trusted users only and consider deploying a WAF rule to block serialized data patterns in HTTP requests.

Recommended fix Moderate confidence

Latest version of PDF for WPForms (version higher than 6.5.0)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'PDF for WPForms' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is functioning correctly by testing form PDF generation
  6. 6. Consider reviewing the plugin's changelog or the vendor's advisory for any specific security details
Caveat Review plugin changelog before upgrading; ensure compatibility with your WPForms version and WordPress core

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-60082 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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