Security readout for executives and security teams
Plain-English summary
A flaw in Popup by Supsystic could let an internet-based, unauthenticated attacker submit malicious data that WordPress processes as a PHP object. The supplied assessment indicates possible theft or alteration of data and service disruption. Sites using plugin version 1.13.0 or earlier should be investigated urgently.
Executive priority
Treat this as an urgent identification and containment issue because exploitation requires no account or user interaction and the stated impact spans data confidentiality, integrity, and availability. Prioritize public-facing sites first. Current evidence does not confirm attacks or name a fixed version, so remediation decisions should follow verified vendor or Patchstack guidance.
Technical view
CVE-2026-73380 is a CWE-502 PHP Object Injection vulnerability affecting Popup by Supsystic through version 1.13.0. Its CVSS 3.1 vector indicates network access, low complexity, no privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impacts. The supplied sources do not identify the vulnerable endpoint or required object chain.
Likely exposure
Exposure is most likely on internet-reachable WordPress installations with Popup by Supsystic version 1.13.0 or earlier enabled. The bundle contains inconsistent structured version metadata—“n/a” and a default status of “unaffected”—but its title and description explicitly identify versions through 1.13.0 as vulnerable.
Exploitation context
The supplied bundle does not establish active exploitation, and its KEV indicator is false. It also provides no evidence about public proof-of-concept code, observed attacks, or exploitation prerequisites beyond the unauthenticated network-accessible condition. Do not interpret this absence as evidence that exploitation is impossible.
Researcher notes
The record supports an unauthenticated PHP Object Injection classification and critical CVSS score, but lacks endpoint details, data-flow evidence, gadget-chain requirements, exploit telemetry, and remediation information. The structured affected entry conflicts with the narrative version range. Researchers should validate the range against authoritative updates without assuming remote code execution or a specific exploitation outcome.
Mitigation direction
- Inventory all WordPress installations for the Popup by Supsystic plugin.
- Check Supsystic and Patchstack guidance for a confirmed fixed release or official mitigation.
- Apply a vendor-confirmed non-affected version as soon as one is identified.
- Disable or remove the plugin if no confirmed safe version exists and business operations permit.
Validation and detection
- Record each installation’s plugin version, activation status, and internet accessibility.
- Confirm versions 1.13.0 and earlier are upgraded, disabled, or removed.
- Verify the selected replacement version is explicitly identified as non-affected by authoritative guidance.
- Review available web and application logs, recognizing that the sources provide no detection signature.
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-73380 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/popup-by-supsystic/vulnerability/wordpress-popup-by-supsystic-plugin-1-13-0-php-object-injection-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.