CVE-2024-12637
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 Moving Users plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.05 via the export functionality. The JSON files are stored in predictable locations with guessable file names when exporting user data. This could allow unauthenticated attackers to extract sensitive user data, for instance, email addresses, hashed passwords, and IP addresses.
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 confidenceThe Moving Users WordPress plugin (versions up to 1.05) stores exported user data as JSON files in predictable, guessable locations accessible via direct URL. This allows unauthenticated attackers to enumerate and download these files, extracting sensitive data including email addresses, hashed passwords, and IP addresses.
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.
-
Verify Moving Users plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Moving Users' or check the plugins directory (wp-content/plugins/moving-users) via file systemAffected if The plugin is installed and active
-
Check installed plugin versionView the plugin's main PHP file header or check the WordPress plugin repository for the version numberAffected if Version is 1.05 or lower (any version up to and including 1.05 is affected)
-
Look for exported JSON filesSearch the wp-content/uploads directory and any plugin-specific export directories for .json files containing user data (look for files with fields like email, password, IP addresses)Affected if Any JSON files containing user export data exist on the server
-
Test web accessibility of export directoryAttempt to access common export paths (such as wp-content/uploads/moving-users/ or similar predictable locations) via HTTP request to see if files are directly downloadableAffected if The export directory or JSON files are accessible via direct URL without authentication
-
Review web server access logsSearch access logs for requests to .json files in plugin-related paths, especially from unauthenticated or external IP addressesAffected if Logs show unauthorized access to JSON export files
A user is affected if the Moving Users plugin versions 1.05 or below is installed and JSON export files exist and are accessible via web without authentication.
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.
From vendor dataDisable or remove the export functionality until a patched version is available, or implement .htaccess rules to block direct access to the export directory and add authentication checks to the export endpoint.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12637 — 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-2024-12637 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