# CVE-2025-22973: Information disclosure in n/a

> A remote attacker can obtain sensitive information from QiboCMS via the http_curl function in the common PHP file.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 20 Feb 2025
- **Updated:** 21 Feb 2025
- **Also known as:** GHSA-44g2-wmg5-f6v6

## What is CVE-2025-22973?

CVE-2025-22973 is a high-severity vulnerability in n/a, published on 20 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in QiboSoft QiboCMS X1.0 allows a remote attacker to obtain sensitive information via the http_curl() function in the '/application/common. php' file that directly retrieves the URL request response content.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-22973?

It affects 1 product.


Products: Qibosoft Qibocms X1.

## How do I fix CVE-2025-22973?

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

## Is CVE-2025-22973 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-1225](https://insights.sbomify.com/CVE-2024-1225/): QiboSoft QiboCMS X1 Pay.php rmb_pay deserialization (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22973 and fix it if it is affected.

What it is: CVE-2025-22973 is a high-severity vulnerability in n/a, published on 20 Feb 2025. 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-2025-22973 in the wild and no public exploit code.

Affected product: n/a. 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-2025-22973/ (Markdown: https://insights.sbomify.com/CVE-2025-22973/index.md)
```

## Sources

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

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