dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-25917

HIGH · 8.8 CVSS v3.1 Published 2024-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Information to an Unauthorized Actor vulnerability in CodeRevolution WP Setup Wizard.This issue affects WP Setup Wizard: from n/a through 1.0.8.1.

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

An information disclosure vulnerability in CodeRevolution WP Setup Wizard plugin for WordPress allows unauthorized actors to access sensitive information. The specific attack vector and exact data exposed are not detailed in the available description, but the high CVSS score indicates significant impact.

MitigationUpdate WP Setup Wizard to the latest version beyond 1.0.8.1 when available, or disable and remove the plugin until a patched version can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 the plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'CodeRevolution WP Setup Wizard' or check the /wp-content/plugins/ directory for a folder named 'wp-setup-wizard' or similar
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed version
    In the Plugins list, find the CodeRevolution WP Setup Wizard entry and note the version number displayed beneath the plugin name, or inspect the main plugin file header in /wp-content/plugins/[plugin-folder]/[main-file].php for the 'Version' tag
    Affected if The version is 1.0.8.1 or lower (versions up to and including 1.0.8.1 are affected)
  3. Confirm the plugin is active
    Check the Plugins admin page - if the plugin shows as 'Active' under the plugin status column, it is currently enabled
    Affected if The plugin is activated and running on the WordPress site
  4. Review access logs for suspicious requests
    Examine web server access logs (Apache error.log, Nginx access.log) or WordPress security plugins for unusual GET/POST requests to /wp-content/plugins/wp-setup-wizard/ endpoints or similar paths
    Affected if Unusual or unauthorized requests to plugin endpoints are present in logs

A WordPress site is affected if the CodeRevolution WP Setup Wizard plugin is installed, active, and running version 1.0.8.1 or lower.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP Setup Wizard to the latest version beyond 1.0.8.1 when available, or disable and remove the plugin until a patched version can be applied.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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