# CVE-2023-3601: Simple Author Box < 2.52 - Contributor+ Arbitrary User Information Disclosure via IDOR

> Contributors can view arbitrary user information due to missing ID verification in the Simple Author Box plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 14 Aug 2023
- **Updated:** 5 May 2025
- **Also known as:** GHSA-x9pq-rg5g-m83p

## What is CVE-2023-3601?

CVE-2023-3601 is a medium-severity vulnerability in Unknown Simple Author Box, published on 14 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Simple Author Box WordPress plugin before 2.52 does not verify a user ID before outputting information about that user, leading to arbitrary user information disclosure to users with a role as low as Contributor.

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

It affects 1 product.


Products: Webfactoryltd Simple Author Box.

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

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

## Is CVE-2023-3601 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-3601 is a medium-severity vulnerability in Unknown Simple Author Box, published on 14 Aug 2023. 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-3601 exists.

Affected product: Unknown Simple Author Box. 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-3601/ (Markdown: https://insights.sbomify.com/CVE-2023-3601/index.md)
```

## Sources

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

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