HarborGuardharborguardDatabase
Back to search
HIGHCVE-2026-39498Published Modified CNA Patchstack

CVE-2026-39498: WordPress YayMail plugin <= 4.3.3 - PHP Object Injection vulnerability

Shop manager PHP Object Injection in YayMail <= 4.3.3 versions.

Metrics

CVSS v3.1
7.2
Severity
HIGH
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 an attacker supplies a crafted serialized PHP string that the application deserializes, potentially triggering arbitrary code execution through gadget chains already present in the codebase. The YayMail WordPress plugin (versions 4.3.3 and below) is reachable over the network and requires a shop manager-level account to exploit. Successful exploitation gives the attacker full control over confidentiality, integrity, and availability of the affected environment. No fix has been published yet; HarborGuard tracks this advisory and will make a patched-image rebuild available the moment an upstream fix is released.

HarborGuard Coverage

Detection

Detection for CVE-2026-39498 is available across every HarborGuard environment, with the CVE matched against customer images within minutes of ingestion from upstream advisory feeds, including Patchstack. Coverage extends to custom-built container images that bundle the YayMail plugin alongside WordPress, not just images pulled from public registries.

Available
Triage

HarborGuard is capable of scoring this CVE at 7.2 HIGH (CVSS v3.1) and weighting that score against each environment's compliance policy to determine priority. Triage routing to the appropriate team inbox within each customer organization is available as part of the standard pipeline.

Available
Patch

Because no fix version has been published for CVE-2026-39498, HarborGuard re-checks the advisory on every ingest cycle and will make a patched-image rebuild available automatically the moment an upstream fix appears. In the interim, compensating controls such as network policy restrictions on affected workloads are surfaced as actionable suggestions within the HarborGuard dashboard.

Pending upstream

Exploit Conditions

  • Network reachabilityRequired

    The vulnerable endpoint is exposed over the network, so an attacker must be able to reach the WordPress installation via HTTP/HTTPS.

  • AuthenticationRequired

    A shop manager-level account (or higher) is required; a low-privilege standard subscriber account is not sufficient.

  • Victim interactionNot required

    No victim interaction is needed; the attacker can trigger the vulnerability directly once authenticated.

  • Attack complexityDetail

    Attack complexity is low, meaning the exploit is reliable and does not depend on race conditions or specific environmental layout.

Blast Radius

  • Reads sensitive data stored in the WordPress database, including order records, customer details, and configuration secrets.
  • Modifies or deletes persisted database content, including plugin settings, user records, and order data.
  • Executes arbitrary PHP code on the server through deserialization gadget chains, enabling full host-level compromise.
  • Crashes or destabilizes the WordPress application, causing service disruption for storefront visitors and administrators.

How HarborGuard Handles This

Available on HarborGuard: because no upstream fix exists for CVE-2026-39498 at this time, HarborGuard continuously re-evaluates the advisory on every ingest cycle and will trigger a patched-image rebuild automatically when a fix version is published. For customers who opt into auto-remediation, that rebuild will be followed by a regression test run and a PR opened against affected workloads. While no patch is available, HarborGuard surfaces compensating-control recommendations including network policy isolation to restrict inbound access to the WordPress admin and WooCommerce shop-manager endpoints, egress filtering to limit outbound calls from the container, and feature-flag or plugin-deactivation guidance where the customer's deployment model permits. Where compliance policy permits, affected images are flagged for mandatory review and hold gates in the CI pipeline until the upstream fix is incorporated.

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