CVE-2025-41106
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 · uneditedHTML injection vulnerability found in Fairsketch's RISE CRM Framework v3.8.1, which consist of an HTML code injection due to lack of proper validation of user inputs by sending a POST request in parameter 'first_name' in '/clients/save_contact/'.
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 · moderate confidenceHTML injection vulnerability in RISE CRM Framework v3.8.1 where the 'first_name' POST parameter in the '/clients/save_contact/' endpoint lacks proper input validation, allowing attackers to inject arbitrary HTML code into the application.
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< 3.9CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 the installed Rise CRM versionAccess the application admin panel and navigate to Settings > App Info or check the version number displayed in the footer of the application interface. Alternatively, check the version file in the application installation directory if accessible.Affected if The installed version is 3.8.1 or any version prior to 3.9
-
Verify the /clients/save_contact/ endpoint existsCheck if the application has client management functionality enabled. Attempt to access or analyze the application's URL routing for the /clients/save_contact/ endpoint. This is typically found in the Clients module under Contact Persons or Team Members.Affected if The endpoint exists and is accessible within the application
-
Confirm client contact creation functionality is enabledNavigate to the Clients section in the application and check if the ability to add new contact persons is available. Verify the 'first_name' field exists in the contact creation form.Affected if Users can access the contact creation form with a 'first_name' input field
-
Test for HTML injection in the first_name parameterSubmit a POST request to /clients/save_contact/ with an HTML payload in the first_name parameter (e.g., <script>alert(1)</script>). This requires authenticated access to the client management feature. Inspect the response and subsequent pages where the contact name is displayed.Affected if The submitted HTML code is rendered unescaped in the application output (e.g., in the contacts list or contact details page)
A user is affected if they are running Fairsketch Rise Ultimate Project Manager version 3.8.1 or any version below 3.9 and have the client contact management feature accessible to users who can submit the first_name parameter without proper sanitization.
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.
dbcve · scoped3.9
Implement strict input validation and output encoding for the 'first_name' parameter and all user-supplied data. Sanitize or escape HTML characters before storage and before rendering in any output context.
3.9
- 1. Verify current installation version by checking the application footer or admin dashboard
- 2. Create a complete backup of the database and application files
- 3. Download RISE Ultimate Project Manager version 3.9 from the official Fairsketch marketplace or distribution channel
- 4. Upload and install the version 3.9 package following standard upgrade procedures
- 5. Test the /clients/save_contact/ endpoint to confirm the first_name parameter now properly sanitizes input
- 6. Verify all other client contact functionality works correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41106 — 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-41106 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