# CVE-2025-13493: Missing authorization in Latest Registered Users

> Unauthenticated attackers can export complete user details in CSV format due to missing authorization checks in the Latest Registered Users WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-7q6w-ggv8-84g7

## What is CVE-2025-13493?

CVE-2025-13493 is a high-severity missing authorization vulnerability in webrndexperts Latest Registered Users, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-13493?


## How do I fix CVE-2025-13493?

No fix has been published for CVE-2025-13493 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-13493 being exploited?

There is no known exploitation of CVE-2025-13493 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13493 and fix it if it is affected.

What it is: CVE-2025-13493 is a high-severity missing authorization vulnerability in webrndexperts Latest Registered Users, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13493 in the wild and no public exploit code.

Affected product: webrndexperts Latest Registered Users. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-13493/ (Markdown: https://insights.sbomify.com/CVE-2025-13493/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13493
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13493
- OSV: https://osv.dev/vulnerability/CVE-2025-13493

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13493/
Summaries are generated and may contain mistakes; the official description above is the record.