# CVE-2023-40362: Missing authorization in n/a

> Remote attackers can arbitrarily delete contractors from user accounts due to missing access control protections in the building permit software.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-4mhf-c48q-rghx

## What is CVE-2023-40362?

CVE-2023-40362 is a medium-severity missing authorization vulnerability in n/a, published on 12 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in CentralSquare Click2Gov Building Permit before October 2023. Lack of access control protections allows remote attackers to arbitrarily delete the contractors from any user's account when the user ID and contractor information is known.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-40362?

It affects 1 product.


Products: Centralsquare Click2gov Building Permit.

## How do I fix CVE-2023-40362?

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

## Is CVE-2023-40362 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-40362 exists.

Public exploit code:

- CVE-2023-40362 Vulnerabilitiy details and proof of concept (github_poc): https://github.com/ally-petitt/CVE-2023-40362

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-40362 and fix it if it is affected.

What it is: CVE-2023-40362 is a medium-severity missing authorization vulnerability in n/a, published on 12 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-40362 exists.

Affected product: n/a. 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-2023-40362/ (Markdown: https://insights.sbomify.com/CVE-2023-40362/index.md)
```

## Sources

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

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