# CVE-2023-41683: WordPress TelSender plugin <= 1.14.11 - Broken Access Control + CSRF vulnerability

> Attackers can bypass access controls and perform unauthorized actions via CSRF in the TelSender WordPress plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **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:** 13 Dec 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-8265-386p-5v6c

## What is CVE-2023-41683?

CVE-2023-41683 is a medium-severity missing authorization vulnerability in Pechenki TelSender, published on 13 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in Pechenki TelSender allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects TelSender: from n/a through 1.14.11.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2023-41683 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41683 is a medium-severity missing authorization vulnerability in Pechenki TelSender, published on 13 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-41683 in the wild and no public exploit code.

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

## Sources

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

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