CVE-2025-3104
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 · uneditedThe WP STAGING Pro WordPress Backup Plugin for WordPress is vulnerable to Information Exposure in all versions up to and including 6.1.2 due to missing capability checks on the getOutdatedPluginsRequest() function. This makes it possible for unauthenticated attackers to reveal outdated installed active or inactive plugins.
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 confidenceThe WP STAGING Pro WordPress Backup Plugin (versions up to 6.1.2) lacks proper capability checks on the getOutdatedPluginsRequest() function, allowing unauthenticated attackers to enumerate all installed plugins (both active and inactive) including their versions. This information disclosure aids attackers in identifying vulnerable, outdated plugins for further exploitation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WP STAGING Pro is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WP STAGING Pro' in the list of active plugins.Affected if WP STAGING Pro appears in the installed plugins list
-
Determine the installed versionIn the WordPress admin, go to Plugins > Installed Plugins. Locate WP STAGING Pro and read the version number displayed beneath the plugin name.Affected if The version number is 6.1.2 or lower (any version up to and including 6.1.2)
-
Identify the vulnerable AJAX endpointInspect the plugin files via FTP or file manager. The vulnerable function getOutstandingPluginsRequest() is typically exposed through the wp_ajax_nopriv_ hook, making it accessible to unauthenticated users. Common endpoint pattern: /wp-admin/admin-ajax.php?action=staging_get_outdated_pluginsAffected if The plugin exposes an AJAX action callable without authentication that returns plugin enumeration data
-
Test for information disclosureSend a crafted request to the AJAX endpoint (e.g., curl -X POST https://yourdomain.com/wp-admin/admin-ajax.php -d 'action=staging_get_outdated_plugins') without providing any authentication cookies or credentials.Affected if The response returns a list of installed plugins with their names and version numbers, exposing sensitive enumeration data to unauthenticated users
A WordPress site is affected if it has WP STAGING Pro plugin installed at version 6.1.2 or lower and the plugin's AJAX endpoint is accessible without authentication, allowing unauthenticated plugin enumeration.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate WP STAGING Pro plugin to version 6.1.3 or later which includes proper authorization checks on the affected function. Until then, consider restricting access to the plugin's AJAX endpoints via server-side configuration.
WP STAGING Pro 6.1.3 or later
- Upgrade the WP STAGING Pro plugin to version 6.1.3 or later to patch the missing capability check vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3104 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3104 in production — separate from our analysis above.
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.
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.
- 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