dbcve.org
PopupWordPress extension · Supsystic

CVE-2023-46197

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 1.10.20 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A path traversal vulnerability in the Popup by Supsystic WordPress plugin (versions up to 1.10.19) allows attackers to access files outside the intended directory using relative path sequences (e.g., ../../). This improper limitation of pathname to a restricted directory enables unauthorized file access.

MitigationImplement strict input validation and path sanitization to ensure all file paths resolve within allowed directories, blocking traversal sequences. Update to the latest patched version if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PopupWordPress extension
Affected:< 1.10.20

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Popup by Supsystic plugin version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, find 'Popup by Supsystic' and read the version number displayed below the plugin name. Alternatively, inspect the main plugin file header in wp-content/plugins/popup-by-supsystic/
    Affected if The displayed version is any version below 1.10.20 (e.g., 1.10.19, 1.10.18, etc.)
  2. Verify plugin files exist
    Check that the plugin directory wp-content/plugins/popup-by-supsystic/ exists and contains PHP files. Path traversal vulnerabilities in this plugin stem from improper file handling in the plugin code.
    Affected if The plugin is installed and active, with the vulnerable version range present on the system
  3. Confirm plugin is active
    In WordPress admin, verify the Popup by Supsystic plugin shows as 'Active' status. Path traversal exposure requires the plugin code to be loaded and processing requests.
    Affected if The plugin is active and running

If the installed version of Popup by Supsystic is below 1.10.20 and the plugin is active, the environment is affected by this path traversal vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.10.20 or later
Fixed in 1.10.20
Interim mitigation

Implement strict input validation and path sanitization to ensure all file paths resolve within allowed directories, blocking traversal sequences. Update to the latest patched version if available.

Recommended fix Moderate confidence

version 1.10.20

  1. 1. Backup your WordPress site and database before performing any updates
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Find 'Popup by Supsystic' in the plugin list
  5. 5. If an update is available, click 'Update Now' to update to version 1.10.20
  6. 6. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  7. 7. After updating, verify the plugin version shows 1.10.20
  8. 8. Test that popup functionality works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Popup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46197 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-46197 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data