CVE-2025-41103

5.4 MEDIUM

📋 TL;DR

This CVE describes an HTML injection vulnerability in Fairsketch's RISE CRM Framework v3.8.1. Attackers can inject malicious HTML code via the 'reply_message' parameter in POST requests to '/messages/reply', potentially leading to cross-site scripting attacks. Organizations using this specific version of RISE CRM are affected.

💻 Affected Systems

Products:
  • Fairsketch RISE CRM Framework
Versions: v3.8.1
Operating Systems: Any OS running the web application
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects the specific version mentioned; earlier or later versions may have different security postures.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could execute arbitrary JavaScript in victims' browsers, potentially stealing session cookies, performing actions as authenticated users, or redirecting to malicious sites.

🟠

Likely Case

Attackers inject malicious HTML/JavaScript that executes when users view messages, potentially stealing session data or performing limited actions within the CRM.

🟢

If Mitigated

With proper input validation and output encoding, injected HTML would be rendered as plain text rather than executable code.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires sending POST requests to the vulnerable endpoint with malicious HTML in the 'reply_message' parameter.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-fairsketchs-rise-crm-framework

Restart Required: No

Instructions:

Check vendor website for security updates. If available, apply the patch and verify input validation is properly implemented for the 'reply_message' parameter.

🔧 Temporary Workarounds

Input Validation Filter

all

Implement server-side input validation to sanitize HTML content in the 'reply_message' parameter before processing.

WAF Rule

all

Deploy a web application firewall rule to block POST requests containing suspicious HTML patterns in the 'reply_message' parameter.

🧯 If You Can't Patch

  • Implement strict Content Security Policy (CSP) headers to limit script execution.
  • Disable or restrict access to the '/messages/reply' endpoint if not essential for business operations.

🔍 How to Verify

Check if Vulnerable:

Test by sending a POST request to '/messages/reply' with HTML tags in the 'reply_message' parameter and check if they are rendered as HTML in the response.

Check Version:

Check the CRM framework version in the application's admin panel or configuration files.

Verify Fix Applied:

After applying fixes, test the same injection attempt to confirm HTML is properly escaped or rejected.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to '/messages/reply' containing HTML tags or JavaScript code in parameters.
  • Multiple failed injection attempts from single IP addresses.

Network Indicators:

  • HTTP POST traffic to the vulnerable endpoint with suspicious payloads in the request body.

SIEM Query:

source="web_server_logs" AND uri="/messages/reply" AND method="POST" AND (message="<script>" OR message="javascript:")

🔗 References

📤 Share & Export