Security readout for executives and security teams
Plain-English summary
CVE-2026-73397 is a critical flaw reported in the WordPress Youzify plugin through version 1.3.7. An unauthenticated remote attacker may submit untrusted serialized data, potentially compromising confidentiality, integrity, and availability. The supplied evidence does not identify a safe version or confirmed exploitation.
Executive priority
Treat as an immediate investigation and remediation priority for internet-facing WordPress sites. The 9.8 rating and unauthenticated attack path imply substantial business impact, although exploitation is not established. Require rapid asset inventory, containment where necessary, and confirmation of authoritative vendor remediation.
Technical view
The issue is CWE-502, deserialization of untrusted data, with CVSS 3.1 score 9.8. The vector indicates network access, low complexity, no privileges, and no user interaction. Actual outcomes depend on the vulnerable code path and available object behaviors; the sources provide no technical proof, prerequisites, or exploit details.
Likely exposure
Potentially exposed systems are WordPress sites running Youzify 1.3.7 or earlier where the vulnerable functionality is remotely reachable. Inventory confirmation is essential because the structured affected metadata is incomplete and includes a conflicting default status of unaffected.
Exploitation context
The source bundle marks this CVE as absent from KEV and provides no cited evidence of active exploitation. Its unauthenticated, network-accessible CVSS characteristics nevertheless justify urgent defensive action. Exploit availability and observed attack activity remain unconfirmed.
Researcher notes
The title and description state Youzify through 1.3.7 is affected, but the structured affected entry lists versions as n/a and defaultStatus as unaffected. No patch version, vulnerable endpoint, prerequisites, proof of concept, or exploitation telemetry is supplied. Validate scope against current vendor or Patchstack guidance.
Mitigation direction
- Inventory all WordPress sites and record installed Youzify versions.
- Check Patchstack and Youzify guidance for a confirmed fixed release or mitigation.
- Update to a vendor-confirmed safe version when available.
- Temporarily disable Youzify where exposure cannot be resolved promptly.
- Restrict public access to affected functionality where operationally feasible.
Validation and detection
- Confirm Youzify is absent or newer than the vendor-confirmed affected range.
- Verify the deployed plugin files match the intended release.
- Test that disabling or updating Youzify does not disrupt required site functions.
- Review web and application logs for suspicious requests or unexpected errors.
- Recheck vendor guidance for revised affected versions and remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-73397 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/youzify/vulnerability/wordpress-youzify-plugin-1-3-7-deserialization-of-untrusted-data-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.