dbcve.org
CrmebApplication

CVE-2025-11288

HIGH · 8.8 CVSS v3.1 Published 2025-10-05
Fix available
A fix is available. Upgrade to after 5.6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A security flaw has been discovered in CRMEB up to 5.6. This issue affects some unknown processing of the file /adminapi/product/product of the component GET Parameter Handler. Performing a manipulation of the argument cate_id results in sql injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. 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 confidence

A SQL injection vulnerability exists in CRMEB up to version 5.6 in the /adminapi/product/product endpoint. The cate_id GET parameter is not properly sanitized, allowing attackers to inject malicious SQL commands. This could allow unauthorized access to, modification, or deletion of database contents.

MitigationRestrict network access to the admin API immediately; implement Web Application Firewall rules to block SQL injection patterns; once a vendor patch is available, apply it promptly. Consider parameterized queries or an ORM to remediate the underlying code flaw.

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
CrmebApplication
Affected:<= 5.6

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm CRMEB installation exists
    Look for CRMEB files in your web root directory. Common paths include /var/www/html/, /www/wwwroot/, or the document root configured for your web server. Look for the characteristic CRMEB directory structure.
    Affected if CRMEB is installed on the server
  2. Identify the installed CRMEB version
    Check the version file or configuration. Common locations include a version.php file, config/app.php, or a composer.json file within the CRMEB installation directory. Compare the version number to 5.6.
    Affected if The installed version is 5.6 or lower (any version up to and including 5.6)
  3. Verify the admin API is network accessible
    Test network access to the /adminapi/ path on your CRMEB server. Use curl or a browser to request http(s)://your-domain/adminapi/ and confirm you receive an API response rather than a 403/404.
    Affected if The admin API endpoint is reachable from the network (not restricted to localhost or internal IPs only)
  4. Confirm the vulnerable endpoint exists and is accessible
    Request the endpoint /adminapi/product/product with a simple GET parameter, e.g., http://your-domain/adminapi/product/product?cate_id=1. A successful connection (even if returning an error) confirms the endpoint exists.
    Affected if The /adminapi/product/product endpoint responds to requests (is not disabled or removed)
  5. Check if admin authentication is required for the endpoint
    Attempt the request without authentication headers. If the API returns data or SQL error messages rather than an authentication error (401/403), the endpoint may be accessible without proper authorization.
    Affected if The endpoint accepts requests without requiring valid admin authentication or returns SQL-related error messages

A user is affected if CRMEB version 5.6 or lower is installed AND the /adminapi/product/product endpoint is accessible over the network AND the cate_id parameter can be supplied without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 5.6
Interim mitigation

Restrict network access to the admin API immediately; implement Web Application Firewall rules to block SQL injection patterns; once a vendor patch is available, apply it promptly. Consider parameterized queries or an ORM to remediate the underlying code flaw.

Fix this in Crmeb Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11288 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11288 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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