dbcve.org
Popup BoxWordPress extension · Ays Pro

CVE-2023-27414

MEDIUM · 6.1 CVSS v3.1 Published 2023-06-21
Fix available
A fix is available. Upgrade to 3.4.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Popup Box Team Popup box plugin <= 3.4.4 versions.

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 · high confidence

An unauthenticated reflected cross-site scripting (XSS) vulnerability exists in the Popup Box Team Popup plugin for WordPress versions 3.4.4 and below. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that is reflected back in the application's response, potentially executing in victim's browsers when they visit a crafted URL.

MitigationUpgrade the Popup Box Team Popup plugin to a version newer than 3.4.4, or apply vendor-supplied patches. Until patched, users should avoid clicking untrusted links pointing to affected pages.

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
Popup BoxWordPress extension
Affected:< 3.4.5

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Verify the Ays Pro Popup Box plugin is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Popup Box Team Popup' or 'Ays Pro Popup Box' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list and is activated
  2. Check the installed plugin version
    In the WordPress admin Plugins page, click on the plugin name or view details to locate the version number. Compare it against the affected version range of 3.4.4 and below.
    Affected if The installed version is 3.4.4 or any version lower than 3.4.5
  3. Identify if the vulnerable reflection point is accessible
    Examine the plugin settings or generated popup shortcodes to determine if user-supplied parameters are reflected in the frontend output without sanitization.
    Affected if The plugin is configured to display popups that reflect URL parameters or user input directly in the HTML response without proper escaping
  4. Review access logs for suspicious requests
    Check web server access logs for unusual GET or POST requests to pages displaying popups, looking for patterns containing script tags or HTML elements in query parameters.
    Affected if Logs show requests with malicious JavaScript payloads in URL parameters targeting popup-related pages

The environment is affected if the Ays Pro Popup Box plugin version 3.4.4 or below is installed and active, with the vulnerable reflection endpoint accessible to unauthenticated users.

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 3.4.5 or later
Fixed in 3.4.5
Interim mitigation

Upgrade the Popup Box Team Popup plugin to a version newer than 3.4.4, or apply vendor-supplied patches. Until patched, users should avoid clicking untrusted links pointing to affected pages.

Recommended fix High confidence

3.4.5

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Find the 'Popup Box' plugin in the list
  4. Click 'Update now' if an update is available, or manually download version 3.4.5 from the WordPress plugin repository and upload it
  5. Verify the plugin version shows 3.4.5 after updating
  6. Test that the popup functionality works correctly

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

Fix this in Popup Box Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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