CVE-2026-3328

Frontend Admin by DynamiApps <= 3.28.31 - Authenticated (Editor+) PHP Object Injection via 'post_content' of Admin Form Posts

2026-03-25 14:11
Osvaldo Noe Gonzalez Del Rio (Os)

Strategic Overview

Status
Patched in 3.28.32
Affected Plugin
Frontend Admin by DynamiApps
Affected Version
<= 3.28.31
CVSS
7.2High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2026-3328
View all Frontend Admin by DynamiApps vulnerabilities

At a glance

CVE-2026-3328 is a high-severity Deserialization of Untrusted Data vulnerability in the Frontend Admin by DynamiApps WordPress plugin, affecting versions <= 3.28.31. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 3.28.32; sites on affected versions should update now. Disclosed March 2026, reported by Osvaldo Noe Gonzalez Del Rio (Os).

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-502: Deserialization of Untrusted Data

Frontend Admin by DynamiApps <= 3.28.31 carries this weakness at post_content, and reaching it takes an account at Editor level or above. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.

A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For Frontend Admin by DynamiApps the fix is 3.28.32: builds <= 3.28.31 are affected, anything from 3.28.32 onward is not.

Remediation

Update to version 3.28.32, or a newer patched version

How does WordSec protect against this?

An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Frontend Admin by DynamiApps 3.28.32 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-3328https://www.wordfence.com/threat-intel/vulnerabilities/id/0faa8f07-88c1-4638-9de5-e202807866e1https://nvd.nist.gov/vuln/detail/CVE-2026-3328

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C