{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119615 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-119615 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119615 is a high-severity privilege escalation vulnerability in maltesesolutions Reset Database, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-119615 and fix it if it is affected.\n\nWhat it is: CVE-2026-119615 is a high-severity privilege escalation vulnerability in maltesesolutions Reset Database, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-119615 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: maltesesolutions Reset Database. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-119615/ (Markdown: https://insights.sbomify.com/CVE-2026-119615/index.md)","id":"CVE-2026-119615","markdown":"https://insights.sbomify.com/CVE-2026-119615/index.md","name":"CVE-2026-119615","record":{"aliases":["GHSA-qrxx-fg3m-g5wv"],"analysis":{"component_type":"cms_plugin","exploitable_when_present":false,"fix_type":"no_fix_stated","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","requires_specific_call":false,"summary":"Subscriber-level users can reset the WordPress database and become site administrator; sites using Reset Database should care.","user_interaction":"not_required","vuln_class":"privilege_escalation","vulnerable_functions":["process_reset()"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"Wordfence","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in Reset Database","id":"CVE-2026-119615","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"The Noptin – Newsletter, New Post Notifications \u0026 Email Automation plugin for WordPress is vulnerable to Local File Inclusion in all version","id":"CVE-2026-119616"},"nickname":null,"packages":[],"prev":{"headline":"AshAi sends unrecognized tool errors verbatim to MCP clients and the model, disclosing internal details","id":"CVE-2026-119613"},"products":["Reset Database"],"published":"2026-11-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-11","vendors":["maltesesolutions"]},"summary":"Subscriber-level users can reset the WordPress database and become site administrator; sites using Reset Database should care.","url":"https://insights.sbomify.com/CVE-2026-119615/"}