dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-14476

HIGH · 8.8 CVSS v3.1 Published 2025-12-13
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
The Doubly – Cross Domain Copy Paste for WordPress plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.0.46 via deserialization of untrusted input from the content.txt file within uploaded ZIP archives. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject a PHP Object. The additional presence of a POP chain allows attackers to execute arbitrary code, delete files, retrieve sensitive data, or perform other actions depending on the available gadgets. This is only exploitable by subscribers, when administrators have explicitly enabled that access.

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 Doubly WordPress plugin accepts ZIP archives containing a content.txt file and deserializes data from it without proper validation. Authenticated subscribers with admin-enabled access can upload malicious ZIP files containing crafted content.txt data that triggers PHP Object Injection. A POP chain present in the plugin or surrounding environment enables arbitrary code execution.

MitigationUpdate the plugin to version 1.0.47 or later. If an update is unavailable, disable the plugin or revoke the subscriber access permissions that administrators enabled, as the vulnerability requires this explicit configuration.

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 Doubly plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Doubly' in the list. Alternatively, check the wp-content/plugins/ directory for a folder named 'doubly'.
    Affected if The Doubly plugin is present on the WordPress site
  2. Check installed plugin version
    In WordPress admin Plugins page, click on the Doubly plugin to view its version details. Or read the main plugin file (e.g., doubly.php) and look for the 'Version' header in the plugin comments.
    Affected if Version is present and less than 1.0.47
  3. Determine if subscriber upload capability is enabled
    In WordPress admin, navigate to the Doubly plugin settings. Look for any option that enables subscriber-level access or upload functionality for users with subscriber role. Check WordPress user role settings if the plugin adds custom capabilities.
    Affected if Admin has explicitly enabled subscriber access or subscriber-level upload capability in plugin settings
  4. Confirm subscriber user accounts exist
    In WordPress admin, go to Users > All Users and check if any users with 'Subscriber' role exist. Verify if any subscriber accounts have elevated permissions.
    Affected if Subscriber role users exist and at least one has admin-granted access to the vulnerable feature

Your environment is affected if the Doubly plugin is installed with a version below 1.0.47 AND an administrator has explicitly enabled subscriber access, allowing subscriber-level users to upload ZIP archives containing content.txt files.

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 the plugin to version 1.0.47 or later. If an update is unavailable, disable the plugin or revoke the subscriber access permissions that administrators enabled, as the vulnerability requires this explicit configuration.

Recommended fix Moderate confidence

Latest version of Doubly – Cross Domain Copy Paste plugin (version 1.0.47 or later)

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the 'Doubly – Cross Domain Copy Paste' plugin
  3. 3. Check if an update is available for this plugin
  4. 4. If an update is available, update the plugin to the latest version
  5. 5. After updating, verify that subscriber access settings are appropriately configured under the plugin settings
  6. 6. If no update is available through the WordPress admin, download the latest version from the official WordPress plugin repository at plugins.trac.wordpress.org

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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