CVE-2025-53990
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 jetmonsters JetFormBuilder jetformbuilder allows Object Injection.This issue affects JetFormBuilder: from n/a through <= 3.5.1.2.
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 confidenceThis is a PHP Object Injection vulnerability in the JetFormBuilder WordPress plugin. The plugin's use of PHP's unserialize() function on untrusted data allows attackers to inject malicious PHP objects, potentially leading to remote code execution if suitable 'gadget chains' exist in the application or associated libraries.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Verify JetFormBuilder plugin is installedCheck your WordPress installation's wp-content/plugins directory for the jetformbuilder folder, or view the Plugins page in WordPress admin to confirm JetFormBuilder is active.Affected if JetFormBuilder plugin is present and active in the WordPress installation.
-
Identify installed JetFormBuilder versionOpen the main plugin file (usually jetformbuilder.php) in wp-content/plugins/jetformbuilder/ and locate the version defined in the plugin header comment, or check the Plugins page in WordPress admin for the installed version number.Affected if The installed version is lower than the fixed version released for CVE-2025-53990.
-
Search for vulnerable unserialize() callsUse a code search tool (grep, VS Code search, or similar) within the jetformbuilder plugin directory to find instances of unserialize() being called, particularly on variables that could contain user input such as $_POST, $_GET, $_REQUEST, or database values.Affected if The plugin contains unserialize() calls that process data originating from user input.
-
Identify data sources reaching unserializeTrace the code flow from the unserialize() calls found to determine if form submissions, AJAX requests, or other user-controlled data can reach these functions without sanitization.Affected if User-supplied data from form submissions or HTTP requests can reach the vulnerable unserialize() function.
Your environment is affected if JetFormBuilder is installed with a vulnerable version that contains unserialize() calls processing untrusted user input from form submissions or HTTP requests.
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 JetFormBuilder to the latest version once available. If no update exists, audit the codebase for any unserialize() calls handling user input and replace with safe alternatives like json_decode.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53990 — 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-53990 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