# CVE-2026-9172: Devs Accounting <= 1.2.0 - Missing Authorization to Unauthenticated Account Deletion via /delete-account/ REST Endpoint

> Unauthenticated attackers can delete arbitrary accounting records via a REST endpoint lacking permission checks in the Devs Accounting WordPress plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-3vrh-gvf2-896w

## What is CVE-2026-9172?

CVE-2026-9172 is a medium-severity missing authorization vulnerability in ajitdas Devs Accounting – Simple Accounting and Invoicing Solution, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Devs Accounting – Simple Accounting and Invoicing Solution plugin for WordPress is vulnerable to unauthorized modification/deletion of data due to a missing capability check on the delete_single_account() function in versions up to, and including, 1.2.0. The REST route 'devs-accounting/v1/delete-account/(?P<id>\d+)' is registered without any permission_callback, which causes WordPress to expose the endpoint to public, unauthenticated access. This makes it possible for unauthenticated attackers to soft-delete arbitrary accounting account records (wp_dac_accounts) by issuing a simple GET request to the endpoint with any account ID.

Weakness: CWE-862 (Missing Authorization)

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


## How do I fix CVE-2026-9172?

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

## Is CVE-2026-9172 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9172 and fix it if it is affected.

What it is: CVE-2026-9172 is a medium-severity missing authorization vulnerability in ajitdas Devs Accounting – Simple Accounting and Invoicing Solution, published on 24 Jun 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-2026-9172 in the wild and no public exploit code.

Affected product: ajitdas Devs Accounting – Simple Accounting and Invoicing Solution. 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-2026-9172/ (Markdown: https://insights.sbomify.com/CVE-2026-9172/index.md)
```

## Sources

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

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