dbcve.org
VulnerabilityAwaiting classification

CVE-2026-12081

MEDIUM · 5.0 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Remotely reachable No privileges 6 weeks old

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
The Database for Contact Form 7, WPforms, Elementor forms WordPress plugin before 1.5.2 does not restrict the PHP classes allowed when unserializing an attacker-supplied form-field value, allowing unauthenticated users to inject arbitrary PHP objects that are instantiated when an administrator views the stored entry. This is an incomplete fix of CVE-2025-7384 and CVE-2026-2599, whose deserialization paths were hardened while the entry-editor file-field path was missed.

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 confidence

The plugin uses unsafe unserialize() on attacker-supplied form-field values without restricting PHP classes, allowing unauthenticated injection of arbitrary PHP objects. When an administrator views the stored entry in the entry-editor file-field path, the deserialized objects are instantiated, potentially leading to POP chain exploitation. This is an incomplete fix where prior CVEs addressed other deserialization paths but missed this specific entry-editor file-field endpoint.

MitigationUpdate to version 1.5.2 or later which properly restricts allowed PHP classes in the unserialize() call for the entry-editor file-field path.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

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. Identify the affected plugin or component
    Locate the plugin/theme directory in your web root (typically wp-content/plugins/) and read the main PHP file's header to find the Name and Version fields, or run 'grep -r "Version:" your-plugin-dir/'
    Affected if The installed version is lower than 1.5.2 or cannot be determined
  2. Verify the entry-editor file-field functionality exists
    Check if a file named entry-editor.php, entry-editor-file-field.php, or similar exists in the plugin's admin directory, and confirm the path includes 'file-field' in the filename
    Affected if The entry-editor file-field file exists and contains an unserialize() call on user-supplied data
  3. Confirm unauthenticated form submissions are accepted
    Review the form-handling code that processes submissions and check if it validates user authentication before calling unserialize() on submitted field values
    Affected if Form submissions process unserialize() on values without requiring authentication
  4. Check the specific unserialize() call for class restrictions
    Open the identified entry-editor file-field file and locate the unserialize() call - inspect whether it uses a second parameter (e.g., ['allowed_classes' => false]) or a whitelist of allowed classes
    Affected if The unserialize() call has no second parameter or allows all classes (no class restriction)
  5. Confirm admin access to stored entries is possible
    Verify that administrators can access the entry viewer/editor interface where stored form entries are displayed, which triggers the deserialization
    Affected if Admin users can view stored entries through the entry-editor file-field path

You are affected if your installed version is below 1.5.2 and the entry-editor file-field file contains an unrestricted unserialize() call on user-submitted data that gets processed when admins view stored entries.

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 to version 1.5.2 or later which properly restricts allowed PHP classes in the unserialize() call for the entry-editor file-field path.

Recommended fix High confidence

1.5.2

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'The Database for Contact Form 7, WPforms, Elementor forms' plugin
  4. Click 'Update now' if an update is available, or manually update to version 1.5.2
  5. Verify the plugin version shows 1.5.2 or higher after updating

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12081 — 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-2026-12081 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