# CVE-2023-41875: WordPress WP Directory Kit plugin <= 1.2.6 - Broken Access Control vulnerability

> Attackers can bypass access controls in WP Directory Kit to perform unauthorized actions due to missing authorization checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 13 Dec 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-689c-7x7v-4xm7

## What is CVE-2023-41875?

CVE-2023-41875 is a medium-severity missing authorization vulnerability in wpdirectorykit.com WP Directory Kit, published on 13 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in wpdirectorykit.com WP Directory Kit allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Directory Kit: from n/a through 1.2.6.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Wpdirectorykit Wp Directory Kit.

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

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

## Is CVE-2023-41875 being exploited?

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

## Other vulnerabilities in wpdirectorykit.com WP Directory Kit

- [CVE-2025-13390](https://insights.sbomify.com/CVE-2025-13390/): WP Directory Kit <= 1.4.4 - Authentication Bypass to Privilege Escalation via Account Takeover (critical 10.0)
- [CVE-2023-2278](https://insights.sbomify.com/CVE-2023-2278/): WP Directory Kit <= 1.1.9 - Unauthenticated Local File Inclusion via wdk_public_action (critical 9.8)
- [CVE-2024-3217](https://insights.sbomify.com/CVE-2024-3217/): WP Directory Kit <= 1.3.0 - Authenticated (Subscriber+) SQL Injection (high 8.8)
- [CVE-2024-37487](https://insights.sbomify.com/CVE-2024-37487/): WordPress WP Directory Kit plugin <= 1.3.5 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)
- [CVE-2024-29774](https://insights.sbomify.com/CVE-2024-29774/): WordPress WP Directory Kit plugin <= 1.2.9 - Reflected Cross Site Scripting (XSS) vulnerability (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41875 is a medium-severity missing authorization vulnerability in wpdirectorykit.com WP Directory Kit, published on 13 Dec 2024. 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-2023-41875 in the wild and no public exploit code.

Affected product: wpdirectorykit.com WP Directory Kit. 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-41875/ (Markdown: https://insights.sbomify.com/CVE-2023-41875/index.md)
```

## Sources

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

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