HarborGuardharborguardDatabase
Back to search
CRITICALCVE-2026-27429Published Modified CNA Patchstack

CVE-2026-27429: WordPress Nifty theme <= 1.4.1 - PHP Object Injection vulnerability

Unauthenticated PHP Object Injection in Nifty <= 1.4.1 versions.

Metrics

CVSS v3.1
9.8
Severity
CRITICAL
Fixed in
Affected Products
1

Get notified

Email me when this CVE is updated: new fix versions, severity changes, or any record change.

HarborGuard Analysis

Synopsis

PHP Object Injection is a class of vulnerability where attacker-supplied data is passed to PHP's unserialize() function without validation, allowing the attacker to instantiate arbitrary PHP objects and chain them into destructive operations. This vulnerability in the Nifty WordPress theme (versions 1.4.1 and earlier) is reachable over the network with no authentication required. Successful exploitation gives an attacker full control over confidentiality, integrity, and availability of the affected site, including the ability to read sensitive data, modify or delete content, and crash the service. HarborGuard is tracking the upstream advisory for patch availability, as no fix version has been published.

HarborGuard Coverage

Detection

Detection is available across every HarborGuard environment: the CVE is ingested from upstream feeds, including Patchstack, within minutes of publication and matched against customer images containing the Nifty theme package, including custom-built WordPress images. Any image layer carrying the affected BoldThemes/Nifty package at version 1.4.1 or earlier is flagged automatically.

Available
Triage

HarborGuard is capable of scoring this finding at CVSS 9.8 Critical and surfacing it with that weight applied against each customer's compliance policy thresholds. Triage routing is available per organization, directing the alert to the team or inbox configured for Critical-severity WordPress findings.

Available
Patch

Because no upstream fix version has been published, HarborGuard re-checks the Patchstack advisory and relevant package feeds on every ingest cycle. The moment a patched release is available, a rebuilt image becomes available on HarborGuard, and for customers with auto-remediation enabled, an automated rebuild, regression run, and PR against affected workloads can be triggered without manual intervention.

Pending upstream

Exploit Conditions

  • Network reachabilityRequired

    The vulnerable deserialization endpoint is exposed over the network, meaning an attacker must be able to send HTTP requests to the WordPress installation but requires no prior foothold on the host.

  • AuthenticationNot required

    No account or session credentials are needed; the injection can be triggered by an unauthenticated request.

  • Victim interactionNot required

    The attacker does not need to trick any user into taking an action; exploitation is entirely server-side.

  • Attack complexityDetail

    Attack complexity is Low, meaning the exploit is reliable and requires no special timing, race conditions, or environmental configuration beyond reaching the service.

Blast Radius

  • A successful attacker reads arbitrary files on the server, including WordPress configuration files that contain database credentials and secret keys.
  • The attacker modifies or deletes database content, including posts, user accounts, and plugin settings.
  • Crafted object chains can execute OS-level commands on the host, giving the attacker a remote shell if a suitable gadget chain exists in the installed PHP environment.
  • The attacker crashes PHP worker processes or exhausts server resources, taking the site offline.

How HarborGuard Handles This

Available on HarborGuard: because no patched version of the Nifty theme exists yet, HarborGuard monitors the Patchstack advisory and all relevant upstream package feeds on every ingest cycle and will make a patched-image rebuild available the moment an upstream fix is published. For customers with auto-remediation enabled, that rebuild will be followed immediately by a regression run and a PR opened against affected workloads. In the interim, compensating controls worth considering include network-policy rules that restrict public access to wp-admin and any endpoints known to invoke unserialize(), egress filtering to limit post-exploitation callback opportunities, and web application firewall rules that reject requests containing serialized PHP payloads. For environments where the Nifty theme is not actively required, disabling or removing the theme package from the image build entirely eliminates the attack surface until an official fix is released.

See how HarborGuard automates this
Affected packages
  • BoldThemes / Nifty
    ≤ 1.4.1
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References