dbcve.org
PopupWordPress extension · Supsystic

CVE-2023-51353

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 1.10.20 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Missing Authorization vulnerability in supsystic Popup by Supsystic popup-by-supsystic allows Exploiting Incorrectly Configured Access Control Security Levels.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

This is a Missing Authorization vulnerability in the Popup by Supsystic WordPress plugin. The plugin fails to properly enforce access control checks, allowing attackers to exploit incorrectly configured security levels. This likely enables unauthenticated or low-privilege users to perform actions that should require higher privileges, potentially leading to remote code execution or site compromise.

MitigationUpdate to the latest version of Popup by Supsystic if a patch is available. Until then, restrict access to the plugin's admin interfaces via web application firewall rules and limit wp-admin/ajax access to authenticated administrators only.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify Supsystic Popup plugin is installed
    Locate the plugin directory at wp-content/plugins/popup-by-supsystic or check the installed plugins list in WordPress admin under Plugins
    Affected if The plugin directory or listing exists in the WordPress installation
  2. Check installed plugin version
    Open the main plugin file (popup-by-supsystic.php) and locate the Version header in the plugin comments, or view the version in WordPress admin plugins list
    Affected if Version is below 1.10.20 (any version from initial release through 1.10.19)
  3. Identify accessible AJAX endpoints
    Review the plugin PHP files for registered AJAX actions using add_action('wp_ajax_') and add_action('wp_ajax_nopriv_') - check if any admin-level functions are hooked to nopriv AJAX hooks
    Affected if Admin functions are hooked to wp_ajax_nopriv_ hooks or lack capability checks (current_user_can) and nonce verification
  4. Test unauthenticated access to admin functions
    Attempt to access or trigger plugin admin functionality (such as popup creation, modification, or settings changes) without logging in or providing authentication credentials
    Affected if Unauthenticated requests succeed in performing actions that should require admin-level privileges

If the Supsystic Popup plugin versions below 1.10.20 are installed and AJAX/admin functions are accessible without proper authorization checks, the environment is affected by this CVE.

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

Update to the latest version of Popup by Supsystic if a patch is available. Until then, restrict access to the plugin's admin interfaces via web application firewall rules and limit wp-admin/ajax access to authenticated administrators only.

Recommended fix High confidence

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 upgrade to version 1.10.20.
  6. 6. Alternatively, you can update manually by downloading version 1.10.20 from the WordPress plugin repository and uploading it via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin is running version 1.10.20 in the Plugins list.

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

Fix this in Popup Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-51353 — 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-51353 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