CVE-2025-10391
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCRMEB up to v5.6.1 contains a server-side request forgery (SSRF) vulnerability in the testOutUrl function of OutAccountServices.php. The push_token_url parameter is not validated, allowing an attacker to induce the server to make arbitrary requests to internal or external resources, potentially accessing sensitive internal services or exfiltrating data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.6.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Crmeb installation and versionLocate the Crmeb installation directory and check the version file (commonly version.php, system.php, or similar version configuration in the application root or application/config directory)Affected if The installed Crmeb version is 5.6.1 or lower
-
Verify OutAccountServices.php existsSearch for OutAccountServices.php in the application source code, typically in application/services or application/admin/services directoryAffected if The file exists and contains the testOutUrl function with the push_token_url parameter handling code
-
Confirm testOutUrl function is presentOpen OutAccountServices.php and locate the testOutUrl function definition to verify it accepts and processes the push_token_url parameterAffected if The function exists and directly uses the push_token_url parameter without validation in the request handling code
-
Check network accessibility of the vulnerable endpointIdentify the route or API endpoint that calls testOutUrl function; typically this may be in admin routes or API routes related to account/push token configurationAffected if The endpoint is accessible (no authentication requirement or accessible to low-privilege users) and accepts user-controlled push_token_url input
If running Crmeb version 5.6.1 or lower with the testOutUrl function present and the endpoint accessible without proper validation, the environment is vulnerable to CVE-2025-10391.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict allowlist validation for the push_token_url parameter, restricting it to trusted domains or IPs only. Additionally, disable or restrict outbound network access from the application server to prevent abuse of SSRF.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10391 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10391 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data