dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-32512

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Edge-Themes Pelicula pelicula-video-production-and-movie-theme allows Object Injection.This issue affects Pelicula: from n/a through < 1.10.

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

The Pelicula WordPress theme contains a deserialization vulnerability where untrusted data is being unserialized, allowing attackers to inject PHP objects. This can lead to remote code execution through PHP magic methods like __destruct or __wakeup that get triggered upon object destruction.

MitigationUpdate the Pelicula theme to version 1.10 or later to obtain the patched version. If an update is not available, consider removing the theme or implementing input validation to block serialized data.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Pelicula theme is installed
    Navigate to Appearance > Themes in the WordPress admin dashboard and verify the Pelicula theme is listed among installed themes.
    Affected if The Pelicula theme appears in the installed themes list.
  2. Identify installed Pelicula theme version
    Access the theme's style.css file via FTP or file manager at wp-content/themes/pelicula/style.css and locate the 'Version:' header in the CSS comment block at the top of the file.
    Affected if The version listed is lower than 1.10 (for example, 1.9, 1.8, or any version before 1.10).
  3. Check for vulnerable deserialization code
    Search theme source files for unserialize() function calls. In wp-content/themes/pelicula/, use grep or search within PHP files for patterns like 'unserialize($_', 'unserialize($', or 'base64_decode' combined with 'unserialize'.
    Affected if Code containing unserialize() accepting raw user input (from $_GET, $_POST, $_REQUEST, or similar superglobals) is found in the theme files.
  4. Verify exposure of deserialization endpoint
    Review theme files (particularly functions.php or any AJAX handlers) to identify if there are endpoints that accept and process serialized data without validation. Check for request parameters being passed directly to unserialize().
    Affected if Theme files contain code that processes serialized data from HTTP requests without sanitization.

The environment is affected if the Pelicula WordPress theme is installed with a version lower than 1.10 AND the theme contains code that directly unserializes user-supplied input from HTTP requests.

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 Pelicula theme to version 1.10 or later to obtain the patched version. If an update is not available, consider removing the theme or implementing input validation to block serialized data.

Recommended fix Moderate confidence

Pelicula theme version 1.10 or higher

  1. Log into the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. If a newer version of the Pelicula theme is available, click on the theme and select 'Update Now'
  4. If no update is available in WordPress, download the latest version (1.10 or higher) from the theme vendor (Edge-Themes)
  5. Go to Appearance > Themes > Add New > Upload Theme
  6. Upload and install the updated theme package
  7. After updating, verify the theme version shows 1.10 or higher in Appearance > Themes
Caveat Review theme customizations and child theme compatibility after upgrade as custom styling or functionality may need adjustment

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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