PopupWordPress extension · Supsystic

CVE-2023-39997

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-13

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

NVD · unedited

Missing Authorization vulnerability in supsystic.com 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

dbcve analysis · high confidence

A missing authorization vulnerability in the Popup by Supsystic WordPress plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to sensitive administrative functions or data due to improper or missing capability checks.

MitigationUpdate Popup by Supsystic to the latest version that includes proper authorization checks, or implement role-based capability verification at all sensitive endpoints and functions within the plugin.

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

Affected products & versions

NVD · CPE data

PopupWordPress extension

Affected:< 1.10.20

CVSS breakdown

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?

dbcve checks

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

Identify if the Supsystic Popup plugin is installed

Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a folder named 'popup-by-supsystic' or similar.

Affected if The plugin folder exists in the WordPress installation.
Check the installed plugin version

In the WordPress admin under Plugins > Installed Plugins, find the Popup by Supsystic plugin and note the version number displayed below the plugin name. Alternatively, open the main plugin PHP file (usually popup-by-supsystic/popup-by-supsystic.php) and locate the 'Version' header in the plugin comment block.

Affected if The version number displayed is less than 1.10.20.
Verify the plugin is active

In the WordPress admin under Plugins > Installed Plugins, confirm that the Popup by Supsystic plugin shows as 'Active' rather than 'Inactive' or 'Must-Use'.

Affected if The plugin is currently active and the version is below 1.10.20.
Check for unauthorized access to admin functions

Review the plugin's AJAX handlers and admin pages by examining the plugin directory for files containing 'add_action' or 'add_filter' hooks with 'admin_init', 'wp_ajax_', or 'init' hooks that may lack 'current_user_can' or 'check_admin_referer' capability checks.

Affected if Sensitive administrative actions or data endpoints exist without proper capability verification checks.

A WordPress installation is affected if the Popup by Supsystic plugin is active and its installed version is below 1.10.20.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 1.10.20 or later

Fixed in 1.10.20

Interim mitigation

Update Popup by Supsystic to the latest version that includes proper authorization checks, or implement role-based capability verification at all sensitive endpoints and functions within the plugin.

Recommended fix Moderate confidence

1.10.20

Backup your WordPress site before making any changes
Update the Popup by Supsystic plugin to version 1.10.20 or later
Verify the plugin version has been successfully updated in your WordPress admin panel
Test that popup functionality works as expected after the update

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

Fix this in Popup Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

14.0 hours of engineering $2,490

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

patchstack.comThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2023-39997?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 1.10.20 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 0.7%

Affects: Popup

Remediation

A high-priority fix

Fix this in Popup 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2023-39997 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References