# CVE-2023-0335: WP Shamsi <= 4.3.3 - Subscriber+ Attachment Deletion

> Subscribers can delete attachments due to missing authorization and CSRF flaws in the WP Shamsi plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 27 Mar 2023
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-jhxw-3422-m7cw

## What is CVE-2023-0335?

CVE-2023-0335 is a medium-severity missing authorization vulnerability in Unknown WP Shamsi, published on 27 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Shamsi WordPress plugin through 4.3.3 has CSRF and broken access control vulnerabilities which leads user with role as low as subscriber delete attachment.

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Wpvar Wp Shamsi.

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

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

## Is CVE-2023-0335 being exploited?

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

## Other vulnerabilities in Unknown WP Shamsi

- [CVE-2022-4555](https://insights.sbomify.com/CVE-2022-4555/): WP Shamsi <= 4.1.0 - Missing Authorization to Arbitrary Plugin Deactivation (medium 6.5)
- [CVE-2022-38058](https://insights.sbomify.com/CVE-2022-38058/): WordPress WP Shamsi plugin <= 4.1.1 - Authenticated Plugin Setting change vulnerability (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-0335 is a medium-severity missing authorization vulnerability in Unknown WP Shamsi, published on 27 Mar 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-0335 exists.

Affected product: Unknown WP Shamsi. 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-0335/ (Markdown: https://insights.sbomify.com/CVE-2023-0335/index.md)
```

## Sources

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

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