# CVE-2024-1225: QiboSoft QiboCMS X1 Pay.php rmb_pay deserialization

> Remote attackers can achieve code execution in QiboCMS X1 via unsafe deserialization in the Pay.php controller.

- **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:** 5 Feb 2024
- **Updated:** 15 May 2025
- **Also known as:** GHSA-5rfj-4v26-hqmw

## What is CVE-2024-1225?

CVE-2024-1225 is a high-severity unsafe deserialization vulnerability in QiboSoft QiboCMS X1, published on 5 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as critical was found in QiboSoft QiboCMS X1 up to 1.0.6. Affected by this vulnerability is the function rmb_pay of the file /application/index/controller/Pay.php. The manipulation of the argument callback_class leads to deserialization. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-252847. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Qibosoft Qibocms X1.

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

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

## Is CVE-2024-1225 being exploited?

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

## Other vulnerabilities in QiboSoft QiboCMS X1

- [CVE-2025-22973](https://insights.sbomify.com/CVE-2025-22973/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1225 is a high-severity unsafe deserialization vulnerability in QiboSoft QiboCMS X1, published on 5 Feb 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-2024-1225 in the wild and no public exploit code.

Affected product: QiboSoft QiboCMS X1. 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-1225/ (Markdown: https://insights.sbomify.com/CVE-2024-1225/index.md)
```

## Sources

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

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