# CVE-2024-0510: HaoKeKeJi YiQiNiu Api.php http_post server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the YiQiNiu payment API to access internal resources or bypass security controls.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-rx7c-6cwm-h95c

## What is CVE-2024-0510?

CVE-2024-0510 is a high-severity server-side request forgery vulnerability in HaoKeKeJi YiQiNiu, published on 13 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in HaoKeKeJi YiQiNiu up to 3.1. Affected by this issue is the function http_post of the file /application/pay/controller/Api.php. The manipulation of the argument url leads to server-side request forgery. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-250652.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Haokekeji Yiqiniu.

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

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

## Is CVE-2024-0510 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0510 is a high-severity server-side request forgery vulnerability in HaoKeKeJi YiQiNiu, published on 13 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0510 exists.

Affected product: HaoKeKeJi YiQiNiu. 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-0510/ (Markdown: https://insights.sbomify.com/CVE-2024-0510/index.md)
```

## Sources

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

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