CVE-2023-46197
CVE-2023-46197 is a medium-severity vulnerability in Supsystic Popup with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-22.
Key facts
- Severity: Medium (CVSS 3.x base score 5.3)
- EPSS exploit prediction: 1% (70th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2023-50440
- Weakness: CWE-22
- Affected product: Supsystic Popup
- Published:
- Last modified:
Description
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.
Frequently asked questions
- What is CVE-2023-46197?
- 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.
- How severe is CVE-2023-46197?
- CVE-2023-46197 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
- Is CVE-2023-46197 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2023-46197?
- CVE-2023-46197 affects Supsystic Popup. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2023-46197?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2023-46197 have an EU (EUVD) identifier?
- Yes. CVE-2023-46197 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2023-50440.
- When was CVE-2023-46197 published?
- CVE-2023-46197 was published on 2024-05-17 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:supsystic:popup:*:*:*:*:*:wordpress:*:*
More vulnerabilities in Supsystic Popup
- CVE-2023-3186 — Critical (CVSS 9.8): The Popup by Supsystic WordPress plugin before 1.10.19 has a prototype pollution vulnerability that could allow an…
- CVE-2024-52434 — Critical (CVSS 9.1): Deserialization of Untrusted Data vulnerability in supsystic Popup by Supsystic popup-by-supsystic allows Command…
- CVE-2016-10915 — High (CVSS 8.8): The popup-by-supsystic plugin before 1.7.9 for WordPress has CSRF.
- CVE-2021-24275 — Medium (CVSS 6.1): The Popup by Supsystic WordPress plugin before 1.10.5 did not sanitise the tab parameter of its options page before…
- CVE-2023-39997 — Medium (CVSS 5.3): Missing Authorization vulnerability in supsystic.com Popup by Supsystic allows Exploiting Incorrectly Configured Access…
- CVE-2023-51353 — Medium (CVSS 5.3): Missing Authorization vulnerability in supsystic Popup by Supsystic popup-by-supsystic allows Exploiting Incorrectly…
All CVEs affecting Supsystic Popup →
Other CWE-22 (Path Traversal) vulnerabilities
- CVE-2026-55393 — Critical (CVSS 10.0): Unvalidated pathnames in the web interface in Teledyne FLIR Aware2 versions through 6.9.0.2 (PackBot) and 1.7.9…
- CVE-2026-80155 — Critical (CVSS 10.0): Lantronix SLC8000 before firmware v9.7.0.5, SLC9000 before firmware v9.7.0.2, EMG8500/EMG7500 before firmware v9.7.0.1,…
- CVE-2026-70200 — Critical (CVSS 10.0): Improper limitation of a pathname to a restricted directory ('path traversal') in Azure Logic Apps allows an…
- CVE-2026-85706 — Critical (CVSS 10.0): GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.11.12, 19.0 before 19.0.9,…
- CVE-2026-76606 — Critical (CVSS 10.0): Joomla Extension - fabrikar.com - Path Traversal via image element in Fabrik < 4.7.2.
- CVE-2026-18051 — Critical (CVSS 10.0): The W3 Total Cache WordPress plugin before 2.10.5 does not properly validate the request path it uses to build cache…