CVE-2025-7801
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 vulnerability has been found in BossSoft CRM 6.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /crm/module/HNDCBas_customPrmSearchDtl.jsp. The manipulation of the argument cstid leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.
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 confidenceSQL injection vulnerability in BossSoft CRM 6.0 at /crm/module/HNDCBas_customPrmSearchDtl.jsp. The cstid parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Confirm BossSoft CRM installationSearch for BossSoft CRM installation directories or check web server logs for references to /crm/ path. Common locations: /var/www/html/crm/, C:\inetpub\wwwroot\crm\, or application server webapp directories.Affected if BossSoft CRM is installed on the system
-
Identify BossSoft CRM versionCheck application version information - typically found in about pages, version.txt, or within the application configuration files. The vulnerability affects version 6.0 specifically.Affected if Installed version is BossSoft CRM 6.0
-
Locate vulnerable JSP fileCheck if the file /crm/module/HNDCBas_customPrmSearchDtl.jsp exists in the web application directory. This is the specific endpoint with the SQL injection flaw.Affected if The file HNDCBas_customPrmSearchDtl.jsp exists in the /crm/module/ directory
-
Verify cstid parameter usageReview the JSP file content to confirm the cstid parameter is used in SQL query construction without parameterized queries or input sanitization.Affected if The cstid parameter is directly concatenated into SQL queries without prepared statements or escaping
-
Test parameter vulnerabilityIf accessible, send a crafted request to /crm/module/HNDCBas_customPrmSearchDtl.jsp?cstid=' with SQL syntax to observe database errors or unexpected behavior indicating injection is possible.Affected if The application returns SQL error messages or behaves unexpectedly with malicious cstid input
A user is affected if BossSoft CRM version 6.0 is installed and the vulnerable /crm/module/HNDCBas_customPrmSearchDtl.jsp endpoint exists with the cstid parameter used unsafely in SQL queries.
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 parameterized queries or prepared statements for the cstid parameter. Apply input validation and escaping. Monitor vendor for official patch.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7801 — 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-7801 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