dbcve.org
Rise Ultimate Project ManagerApplication · Fairsketch

CVE-2025-41102

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 '/events/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 · moderate confidence

HTML injection vulnerability in RISE CRM v3.8.1 where the 'title' POST parameter in the '/events/save' endpoint lacks proper input validation, allowing attackers to inject arbitrary HTML code via unsanitized user input.

MitigationImplement strict input validation and output encoding on the 'title' parameter in the '/events/save' endpoint to neutralize malicious HTML content before storage or rendering.

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 installation
    Locate the RISE CRM application in your web server directory. Common paths include /var/www/html/, /home/[user]/public_html/, or C:\inetpub\wwwroot\. Look for files with 'rise', 'crm', or 'project manager' in the name.
    Affected if RISE CRM (Fairsketch Rise Ultimate Project Manager) is found on the server
  2. Determine installed version
    Check the version.php file in the application root directory, or log into the CRM admin panel and navigate to Settings > About or App Info to view the version number.
    Affected if The installed version is 3.8.1 or any version prior to 3.9
  3. Verify the /events/save endpoint exists
    Check if the file application/controllers/Events.php exists and contains a 'save' method, or attempt to access /events/save via HTTP OPTIONS request to confirm the route is registered in the routing configuration.
    Affected if The /events/save endpoint is accessible and responds to requests
  4. Test title parameter for HTML injection
    Send a POST request to /events/save with a test payload in the title parameter such as '<script>alert(1)</script>' or '<img src=x onerror=alert(1)>', then query the stored value via the events list or API to see if the HTML is rendered unchanged.
    Affected if The submitted HTML payload is stored and rendered without encoding or sanitization, indicating the vulnerability is present

You are affected if RISE CRM version is below 3.9 and the /events/save endpoint renders unsanitized HTML from the title parameter.

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 and output encoding on the 'title' parameter in the '/events/save' endpoint to neutralize malicious HTML content before storage or rendering.

Recommended fix Moderate confidence

version 3.9

  1. 1. Back up your current RISE Ultimate Project Manager installation and database.
  2. 2. Download the latest version 3.9 of RISE Ultimate Project Manager from the official vendor (Fairsketch).
  3. 3. Review the vendor's upgrade instructions provided with version 3.9.
  4. 4. Upload and install the new version 3.9 files to your server, following the documented upgrade procedure.
  5. 5. Verify the installation completed successfully.
  6. 6. Test the '/events/save' endpoint to confirm the vulnerability is patched and the title parameter now properly validates/sanitizes input.
Caveat Review vendor release notes for any configuration or breaking changes between your current version and 3.9

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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