dbcve.org
Wp Popup BuilderWordPress extension · Themehunk

CVE-2025-62902

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to after 1.3.6 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in ThemeHunk WP Popup Builder wp-popup-builder allows Retrieve Embedded Sensitive Data.This issue affects WP Popup Builder: from n/a through <= 1.3.8.

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 an information disclosure vulnerability in the ThemeHunk WP Popup Builder WordPress plugin (versions up to 1.3.8). The plugin allows unauthorized users to retrieve embedded sensitive data that should not be exposed, potentially exposing system information or configuration details to unauthenticated attackers.

MitigationImplement proper access controls and authentication requirements on endpoints that expose sensitive data. Review and remove any sensitive information that may be embedded in popup configurations.

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
Wp Popup BuilderWordPress extension
Affected:<= 1.3.6

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Verify the plugin is installed
    Check the WordPress plugins directory or use wp-cli: wp plugin list --status=active --field=name | grep -i popup or inspect /wp-content/plugins/ directory for themehunk-wp-popup-builder folder
    Affected if The plugin folder themehunk-wp-popup-builder exists in the plugins directory
  2. Determine the installed version
    Check the plugin main file header in /wp-content/plugins/themehunk-wp-popup-builder/thwp-popup.php for 'Version:' value, or use: wp plugin get thwp-popup --field=version
    Affected if The version number returned is less than or equal to 1.3.6 (or 1.3.8 depending on fixed version in use)
  3. Identify accessible AJAX or REST endpoints
    Review the plugin PHP files for registered hooks: grep -r 'add_action.*wp_ajax' or 'register_rest_route' within the plugin folder, note endpoints that do NOT use 'nopriv' capability checks
    Affected if Endpoints exist that are registered without capability checks or without requiring authentication (no current_user check)
  4. Test for unauthenticated data exposure
    Send a direct HTTP request to identified popup-related endpoints (common patterns: /wp-admin/admin-ajax.php?action=th_popup_, or /wp-json/thwp-popup/v1/) without providing authentication cookies
    Affected if The endpoint returns sensitive system information, configuration data, or popup content without requiring login
  5. Inspect popup configuration storage
    Examine wp_options table or post meta for popup entries: SELECT * FROM wp_options WHERE option_name LIKE '%th%popup%' and review stored values for sensitive data exposure
    Affected if Popup configurations contain sensitive information (API keys, paths, system details) that should not be publicly accessible

A user is affected if the plugin version is <= 1.3.6 and unauthenticated endpoints return sensitive configuration or system data without requiring login

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.

From vendor data
Upgrade available Upgrade to a release after 1.3.6
Interim mitigation

Implement proper access controls and authentication requirements on endpoints that expose sensitive data. Review and remove any sensitive information that may be embedded in popup configurations.

Fix this in Wp Popup Builder 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-2025-62902 — 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-2025-62902 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