# CVE-2025-10391: CRMEB OutAccountServices.php testOutUrl server-side request forgery

> Attackers can exploit a server-side request forgery vulnerability in CRMEB to interact with internal services or external resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 14 Sep 2025
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-8mgm-5xv3-hp87

## What is CVE-2025-10391?

CVE-2025-10391 is a medium-severity server-side request forgery vulnerability in CRMEB, published on 14 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in CRMEB up to 5.6.1. The impacted element is the function testOutUrl of the file app/services/out/OutAccountServices.php. The manipulation of the argument push_token_url leads to server-side request forgery. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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

It affects 1 product.


Products: Crmeb Crmeb.

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

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

## Is CVE-2025-10391 being exploited?

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

## Other vulnerabilities in CRMEB

- [CVE-2025-25763](https://insights.sbomify.com/CVE-2025-25763/): SQL injection in n/a (critical 9.8)
- [CVE-2023-30185](https://insights.sbomify.com/CVE-2023-30185/): File upload in n/a (critical 9.8)
- [CVE-2020-21787](https://insights.sbomify.com/CVE-2020-21787/): File upload in n/a (critical 9.8)
- [CVE-2020-25466](https://insights.sbomify.com/CVE-2020-25466/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-21394](https://insights.sbomify.com/CVE-2020-21394/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10391 is a medium-severity server-side request forgery vulnerability in CRMEB, published on 14 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10391 in the wild and no public exploit code.

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

## Sources

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

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