CVE-2025-13493
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 Latest Registered Users plugin for WordPress is vulnerable to unauthorized user data export in all versions up to, and including, 1.4. This is due to missing authorization and nonce validation in the rnd_handle_form_submit function hooked to both admin_post_my_simple_form and admin_post_nopriv_my_simple_form actions. This makes it possible for unauthenticated attackers to export complete user details (excluding passwords and sensitive tokens) in CSV format via the 'action' parameter.
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 Latest Registered Users WordPress plugin has a broken access control vulnerability in the rnd_handle_form_submit function. The function is hooked to admin_post_my_simple_form and admin_post_nopriv_my_simple_form without any authorization checks or nonce validation, allowing unauthenticated attackers to export all user data (usernames, emails, etc.) in CSV format by submitting a crafted request via the 'action' parameter.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 Latest Registered Users plugin is installedNavigate to WordPress admin Plugins page or inspect /wp-content/plugins/ directory for a folder named 'latest-registered-users' or similarAffected if Plugin is installed and active on the WordPress site
-
Locate the vulnerable function in plugin codeSearch plugin source files for the string 'rnd_handle_form_submit' - check files like main plugin file or includes/admin/ directoryAffected if Function rnd_handle_form_submit exists in the plugin code
-
Check for dangerous admin_post hooksSearch plugin code for 'admin_post_my_simple_form' and 'admin_post_nopriv_my_simple_form' hook registrations using add_actionAffected if Either hook is registered, particularly admin_post_nopriv_my_simple_form which allows unauthenticated access
-
Verify no authorization check exists in the handlerExamine the rnd_handle_form_submit function body for any capability checks (e.g., 'manage_options', 'list_users') or nonce validation before processing user data exportAffected if Function processes export without checking user permissions or validating nonce tokens
Site is affected if the Latest Registered Users plugin is active and contains the rnd_handle_form_submit function hooked to admin_post_nopriv_my_simple_form without capability or nonce checks.
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 dataAdd capability checks (require 'list_users' or similar capability) and nonce validation to the rnd_handle_form_submit function, and remove the admin_post_nopriv hook to prevent unauthenticated access. Update to version 1.5 or later when available.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13493 — 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-13493 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