LiveActive security incident?Get immediate response
CVE Record

CVE-2026-73381: WordPress Popup by Supsystic plugin <= 1.13.0 - Broken Authentication vulnerability

Unauthenticated Broken Authentication in Popup by Supsystic <= 1.13.0 versions.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Popup by Supsystic versions through 1.13.0 reportedly contain a broken authentication flaw. A remote, unauthenticated attacker could make high-impact changes and disrupt an affected WordPress site. The supplied sources report no confidentiality impact, but potentially severe integrity and availability consequences.

Executive priority

Treat confirmed affected, internet-accessible sites as an immediate remediation priority because exploitation requires no authentication or user interaction. Prioritize inventory, containment, and integrity review. Do not claim compromise solely from exposure; the supplied evidence establishes vulnerability risk, not observed exploitation.

Technical view

CVE-2026-73381 is classified as CWE-288 with CVSS 3.1 score 9.1. The vector indicates network access, low complexity, no privileges, and no user interaction. Reported impact is high for integrity and availability, with none for confidentiality. Public technical detail is limited.

Likely exposure

Potential exposure is limited to WordPress sites running Popup by Supsystic through version 1.13.0. The bundle’s structured affected record says versions are unspecified and defaults to unaffected, conflicting with the title and description. Confirm installed versions and deployment status directly.

Exploitation context

The supplied bundle does not identify active exploitation, public exploit code, or inclusion in CISA KEV. KEV is marked false. This does not prove exploitation is absent; it means the provided evidence does not substantiate it.

Researcher notes

Disclosure is sparse and does not describe the authentication failure, vulnerable endpoint, attack behavior, fixed version, or indicators of compromise. The affected-version metadata conflicts with the narrative claim. Avoid inferring mechanisms or testing destructively; obtain authoritative vendor details before concluding remediation is complete.

Mitigation direction

  • Identify every WordPress site with Popup by Supsystic installed or enabled.
  • Check Patchstack and vendor guidance for a confirmed corrected release or official mitigation.
  • Disable or remove affected versions until a verified remediation is available, where operationally feasible.
  • Restrict public access to affected sites if the plugin cannot be disabled safely.
  • Back up sites before remediation and monitor for unauthorized changes or disruption.

Validation and detection

  • Record the plugin version and activation status on every WordPress deployment.
  • Confirm whether each discovered version is 1.13.0 or earlier.
  • Verify the plugin is disabled, removed, or updated according to confirmed vendor guidance.
  • Review WordPress and hosting logs for unexplained administrative actions or availability events.
  • Retest normal site operation after mitigation without attempting exploitation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-288: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2026-73381 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H3.95.2Patchstack

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-73381Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
supsysticPopup by Supsysticpopup-by-supsystic, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-288 · source CWE mapping

Authentication Bypass Using an Alternate Path or Channel

Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.