LiveActive security incident?Get immediate response
CVE Record

CVE-2023-46197: WordPress Popup by Supsystic plugin <= 1.10.19 - Unauthenticated Subscriber Email Addresses Disclosure

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in supsystic.Com Popup by Supsystic allows Relative Path Traversal.This issue affects Popup by Supsystic: from n/a through 1.10.19.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-46197 affects the WordPress Popup by Supsystic plugin through version 1.10.19. An unauthenticated visitor may be able to access subscriber email addresses because of a path traversal weakness. The main business risk is privacy exposure of marketing or subscriber contact data, not site takeover.

Executive priority

Prioritize remediation for public WordPress sites that collect subscriber emails. This is not a critical infrastructure compromise signal, but it can create reportable privacy and trust impact if contact lists were exposed.

Technical view

The issue is classified as CWE-22 relative path traversal in Popup by Supsystic. CVSS 3.1 is 5.3: network exploitable, low complexity, no privileges, no user interaction, unchanged scope, low confidentiality impact, and no integrity or availability impact documented.

Likely exposure

Exposure is limited to WordPress sites running Popup by Supsystic version 1.10.19 or earlier, especially sites using the plugin to collect or store subscriber email addresses.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. The vulnerability is unauthenticated and low complexity, so internet-facing WordPress sites should still treat it as actionable.

Researcher notes

Do not assume broader WordPress compromise from the cited record. The documented impact is subscriber email address disclosure through relative path traversal. The source bundle does not provide endpoint details, proof-of-concept status, or a specific fixed version.

Mitigation direction

  • Inventory WordPress sites for Popup by Supsystic installations.
  • Disable or remove the plugin if version 1.10.19 or earlier is present.
  • Check vendor, WordPress, or Patchstack guidance for a fixed version before re-enabling.
  • Review subscriber data exposure handling requirements with privacy stakeholders.

Validation and detection

  • Confirm the installed Popup by Supsystic version on each WordPress site.
  • Verify whether the site stored subscriber email addresses during the exposure window.
  • Review web logs for suspicious traversal-style requests targeting the plugin.
  • Document whether the plugin was removed, disabled, or updated.
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 · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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 lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-46197 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

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
0Timeline events
0ADP providers
2Source links

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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-46197Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
supsystic.comPopup 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-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.