# CVE-2024-57603: Missing rate limit in MaysWind ezBookkeeping

> Remote attackers can escalate privileges in ezBookkeeping due to missing rate limiting controls.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** Yes
- **Published:** 12 Feb 2025
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-772m-773g-qmhc, GO-2025-3466

## What is CVE-2024-57603?

CVE-2024-57603 is a medium-severity vulnerability in n/a, published on 12 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue in MaysWind ezBookkeeping 0.7.0 allows a remote attacker to escalate privileges via the lack of rate limiting.

Weakness: CWE-799 (Improper Control of Interaction Frequency)

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

3 open source packages ship an affected version, including github.com/mayswind/ezbookkeeping. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/mayswind/ezbookkeeping` | Go | All versions | None |
| `github.com/mayswind/ezbookkeeping` | Go | All versions to 0.7.0 | None |
| `github.com/mayswind/ezbookkeeping` | Go | All versions to 0.7.0 | None |

Products: Mayswind Ezbookkeeping.

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

Upgrade to a fixed version.

## Is CVE-2024-57603 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-57604](https://insights.sbomify.com/CVE-2024-57604/): MaysWind ezBookkeeping has Improper Privilege Management (critical 9.8)
- [CVE-2025-65519](https://insights.sbomify.com/CVE-2025-65519/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-57603 is a medium-severity vulnerability in n/a, published on 12 Feb 2025. 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-2024-57603 exists.

Affected packages and fixed versions:
- github.com/mayswind/ezbookkeeping (Go): affected all versions; no fix listed
- github.com/mayswind/ezbookkeeping (Go): affected all versions up to 0.7.0; no fix listed
- github.com/mayswind/ezbookkeeping (Go): affected all versions up to 0.7.0; no fix listed

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-57603/ (Markdown: https://insights.sbomify.com/CVE-2024-57603/index.md)
```

## Sources

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

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