dbcve.org
Rise Ultimate Project ManagerApplication · Fairsketch

CVE-2025-41103

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 'reply_message' in '/messages/reply'.

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 confidence

HTML injection vulnerability in RISE CRM v3.8.1 allows injection of arbitrary HTML code via the 'reply_message' POST parameter in the /messages/reply endpoint. The application fails to sanitize user input before rendering it, enabling attackers to inject malicious HTML that could lead to cross-site scripting (XSS) attacks.

MitigationImplement proper input validation and output encoding for the 'reply_message' parameter - sanitize all user-supplied content by removing or encoding HTML/script tags before storage and display. Apply context-aware output encoding when rendering user content.

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 RISE CRM version
    Check the installed version by navigating to the admin dashboard's 'Settings > Info' page, or inspect the version.php / version.txt file in the application root directory.
    Affected if The installed version is below 3.9 (e.g., 3.8.1 or earlier)
  2. Confirm messages module is enabled
    Navigate to Settings > Modules or check the database table 'modules' to verify the 'messages' module is enabled for your installation.
    Affected if The messages module is active and accessible to users
  3. Verify reply_message parameter handling
    Submit a test POST request to /messages/reply with a harmless HTML payload in the 'reply_message' parameter (e.g., '<b>test</b>') and observe if the raw HTML renders in the response or is properly encoded/sanitized.
    Affected if The submitted HTML is rendered as-is without encoding or is stored and displayed unsanitized, indicating the vulnerability exists
  4. Check for existing injected content
    Review existing messages in the application database table 'messages' or through the UI to see if any messages contain unescaped HTML or script tags in the reply content.
    Affected if Any stored messages contain raw HTML/script tags that execute or render unescaped

You are affected if running RISE CRM version 3.8.1 or any version below 3.9, the messages module is enabled, and the /messages/reply endpoint reflects the reply_message parameter without proper sanitization.

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 proper input validation and output encoding for the 'reply_message' parameter - sanitize all user-supplied content by removing or encoding HTML/script tags before storage and display. Apply context-aware output encoding when rendering user content.

Recommended fix High confidence

Rise Ultimate Project Manager 3.9

  1. 1. Backup your current Rise Ultimate Project Manager installation and database
  2. 2. Download Rise Ultimate Project Manager version 3.9 or later from the official vendor source
  3. 3. Review the official upgrade instructions provided by Fairsketch for your specific version
  4. 4. Upload and install the new version files, overwriting existing files
  5. 5. Run any provided database migration scripts if included in the update
  6. 6. Verify the installation was successful and test the '/messages/reply' functionality

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

Fix this in Rise Ultimate Project Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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