PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-81344 DynamiApps CVE debrief

The ACF Frontend Admin by DynamiApps WordPress plugin through 3.29.13 does not restrict which PHP classes may be instantiated when it deserialises stored post content that is rendered on public-facing pages, allowing high-privilege users such as administrators to inject a PHP object which, given a suitable POP chain in another installed ACF Frontend Admin by DynamiApps WordPress plugin through 3.29.13 or in WordPress core, can be leveraged to achieve remote code execution.

Vendor
DynamiApps
Product
ACF Frontend Admin
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-17
Original CVE updated
2026-10-17
Advisory published
2026-10-17
Advisory updated
2026-10-17

Who should care

Defenders responsible for WordPress installations, especially those with high-privilege users, should assess exposure and prioritize verification and remediation. This includes administrators, security teams, and vulnerability management teams who need to verify plugin presence, review user access, and plan for potential remediation.

Why it matters

Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations, especially if high-privilege users have access to the plugin, as it may allow remote code execution.

  • Remote code execution may occur if high-privilege users inject a PHP object
  • Verification of plugin presence and user access is necessary
  • Remediation may require updating the plugin to a version that addresses this vulnerability

Technical summary

The ACF Frontend Admin by DynamiApps WordPress plugin through 3.29.13 does not restrict which PHP classes may be instantiated when it deserialises stored post content that is rendered on public-facing pages, allowing high-privilege users such as administrators to inject a PHP object which, given a suitable POP chain in another installed ACF Frontend Admin by DynamiApps WordPress plugin through 3.29.13 or in WordPress core, can be leveraged to achieve remote code execution.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations, especially if high-privilege users have access to the plugin.

Recommended defensive actions

  • Verify the presence of this vulnerability in your WordPress installations
  • Check if high-privilege users have access to the plugin
  • Consider updating the plugin to a version that addresses this vulnerability
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability, but indicate that it exists in the ACF Frontend Admin by DynamiApps WordPress plugin through 3.29.13. Defenders should verify plugin presence, review user access, and check for suitable POP chains in other installed plugins or WordPress core. Evidence is limited, so explicit verification tasks are necessary.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-81344 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-81344

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-81344 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-81344

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.