# CVE-2024-11334: My Contador lesr <= 2.0 - Missing Authorization to Unauthenticated User Registration CSV Export

> Unauthenticated attackers can export user data due to a missing capability check in the My Contador lesr WordPress 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:** 21 Nov 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hrcq-6qf6-8fr9

## What is CVE-2024-11334?

CVE-2024-11334 is a medium-severity missing authorization vulnerability in luydjmi My Contador lesr, published on 21 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The My Contador lesr plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the exportar_registros() function in all versions up to, and including, 2.0. This makes it possible for unauthenticated attackers to export user data.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2024-11334?

It affects 1 product.


Products: Nes360 My Contador Lesr.

## How do I fix CVE-2024-11334?

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

## Is CVE-2024-11334 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11334 and fix it if it is affected.

What it is: CVE-2024-11334 is a medium-severity missing authorization vulnerability in luydjmi My Contador lesr, published on 21 Nov 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-2024-11334 in the wild and no public exploit code.

Affected product: luydjmi My Contador lesr. 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-2024-11334/ (Markdown: https://insights.sbomify.com/CVE-2024-11334/index.md)
```

## Sources

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

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