dbcve.org
Rise Ultimate Project ManagerApplication · Fairsketch

CVE-2025-41105

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 3.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
HTML 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 'title' in '/tickets/save'.

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

HTML injection vulnerability in RISE CRM v3.8.1 allows attackers to inject arbitrary HTML code via the 'title' POST parameter in the /tickets/save endpoint due to insufficient input validation. Successful exploitation could enable stored XSS attacks, potentially leading to session hijacking, defacement, or phishing via malicious HTML/script injection.

MitigationImplement strict input validation with allowlist filtering on the 'title' parameter and apply proper output encoding/escaping when the title is rendered to prevent HTML injection.

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
Rise Ultimate Project ManagerApplication
Affected:< 3.9

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

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

  1. Identify installed RISE CRM version
    Access the admin dashboard or check the application files for the version number. Common locations include the admin panel 'Settings > App Info' or a version.php file in the application root.
    Affected if The installed version is 3.8.1 or any version below 3.9
  2. Confirm tickets module is enabled
    Log in as an administrator and navigate to Settings > Modules or Settings > Permissions to verify the Tickets module is installed and active for user roles.
    Affected if The Tickets module is enabled and accessible to users who can create tickets
  3. Verify endpoint accessibility
    Check if the /tickets/save endpoint is reachable. This typically requires a user account with permission to create tickets. Attempt a request (with harmless test payload) or review application routing configuration.
    Affected if Users can access the /tickets/save endpoint to submit ticket data
  4. Test title parameter for injection susceptibility
    Using an authorized account, submit a POST request to /tickets/save with a test HTML payload in the 'title' parameter (e.g., <script>alert(1)</script>). Then view the ticket to see if the payload renders unescaped.
    Affected if The submitted HTML/script content appears rendered in the ticket view without encoding or validation rejection

A user is affected if their RISE CRM installation is version 3.8.1 or below AND the Tickets module is enabled, allowing unauthorized HTML injection via the title parameter in /tickets/save.

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.

dbcve · scoped
Upgrade available Upgrade to 3.9 or later
Fixed in 3.9
Interim mitigation

Implement strict input validation with allowlist filtering on the 'title' parameter and apply proper output encoding/escaping when the title is rendered to prevent HTML injection.

Recommended fix High confidence

Rise Ultimate Project Manager version 3.9 or later

  1. 1. Backup the current Rise Ultimate Project Manager installation and database
  2. 2. Download version 3.9 or later from the official vendor source
  3. 3. Review the vendor's upgrade documentation for any specific migration requirements
  4. 4. Apply the upgrade following the standard upgrade procedure
  5. 5. Verify the fix by testing the '/tickets/save' endpoint with the 'title' parameter
  6. 6. Confirm the XSS vulnerability is no longer exploitable

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rise Ultimate Project Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41105 — 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-41105 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