# CVE-2025-10390: CRMEB UserAddressServices.php editAddress improper authorization

> Remote attackers can modify user address data by manipulating the ID argument in the editAddress function due to improper authorization checks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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-x9x4-xv57-6g86

## What is CVE-2025-10390?

CVE-2025-10390 is a medium-severity missing authorization 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 weakness has been identified in CRMEB up to 5.6.1. The affected element is the function editAddress of the file app/services/user/UserAddressServices.php. Executing manipulation of the argument ID can lead to improper authorization. The attack may be launched remotely. The exploit has been made available to the public and could be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Crmeb Crmeb.

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

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

## Is CVE-2025-10390 being exploited?

There is no known exploitation of CVE-2025-10390 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-10390 and fix it if it is affected.

What it is: CVE-2025-10390 is a medium-severity missing authorization 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-10390 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-10390/ (Markdown: https://insights.sbomify.com/CVE-2025-10390/index.md)
```

## Sources

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

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