dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-3328

HIGH · 7.2 CVSS v3.1 Published 2026-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 Frontend Admin by DynamiApps plugin for WordPress is vulnerable to PHP Object Injection via deserialization of the 'post_content' of admin_form posts in all versions up to, and including, 3.28.31. This is due to the use of WordPress's `maybe_unserialize()` function without class restrictions on user-controllable content stored in admin_form post content. This makes it possible for authenticated attackers, with Editor-level access and above, to inject a PHP Object. The additional presence of a POP chain allows attackers to achieve remote code execution.

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 Frontend Admin WordPress plugin uses WordPress's maybe_unserialize() on user-controllable content stored in admin_form post types without class restrictions. This allows authenticated attackers with Editor-level or higher privileges to inject arbitrary PHP objects. The presence of a POP (property-oriented programming) chain enables these objects to be manipulated to achieve remote code execution.

MitigationUpdate the Frontend Admin plugin to a version beyond 3.28.31. If an update is unavailable, disable the plugin. Until patched, audit user accounts with Editor-level or higher privileges and consider restricting admin_form post creation capabilities.

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 checks

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

  1. Identify if Frontend Admin plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Frontend Admin' or check the plugin files in wp-content/plugins/frontend-admin/ for the main PHP file and its version header
    Affected if The plugin is present on the site
  2. Determine the installed version of Frontend Admin
    Open the main plugin file (usually frontend-admin.php) and locate the Version header in the plugin comment block, or view the version in the WordPress plugin repository page
    Affected if Version is 3.28.31 or lower
  3. Check for admin_form custom post types
    In WordPress admin, look for a post type named 'admin_form' in the Posts menu, or query the wp_posts table in the database where post_type = 'admin_form'
    Affected if Any admin_form posts exist in the system
  4. Identify users with Editor-level or higher privileges
    In WordPress admin, go to Users and filter by roles 'Editor', 'Author', 'Contributor', 'Administrator', or query wp_usermeta and wp_users tables to list users with wp_capabilities containing editor, author, or administrator
    Affected if Any user accounts with Editor-level or higher privileges exist on the site

The site is affected if Frontend Admin plugin version 3.28.31 or lower is installed, admin_form post types exist, and at least one user with Editor-level or higher privileges is present.

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 Frontend Admin plugin to a version beyond 3.28.31. If an update is unavailable, disable the plugin. Until patched, audit user accounts with Editor-level or higher privileges and consider restricting admin_form post creation capabilities.

Recommended fix Moderate confidence

3.28.32

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Frontend Admin by DynamiApps'
  4. Check if current version is below 3.28.32
  5. If vulnerable, update the plugin to version 3.28.32 or latest available version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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