Skip to main content
VulnerabilityPublished Updated

CVE-2025-61196: CVE-2025-61196 · Code Injection

Affects CVE-2025-61196Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubzsamamah/CVE-2025-61196pkg:github/zsamamah/CVE-2025-61196Other threatsAffected
  • =10.8.3.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor vendor communications closely for official patches or updates addressing CVE-2025-61196 and apply them immediately upon release.
  2. Implement strict input validation and sanitization on the 'comments' parameter at the application and web server layers to block malicious payloads.
  3. Restrict access to the CRMnext application and its interfaces to trusted networks and authenticated users only, employing network segmentation and firewall rules.
  4. Employ application-layer firewalls or web application firewalls (WAFs) with custom rules to detect and block exploitation attempts targeting the vulnerable parameter.
  5. Conduct thorough code reviews and penetration testing focused on input handling to identify and remediate similar injection flaws.
  6. Enforce the principle of least privilege for CRMnext user accounts to minimize the impact of compromised credentials.
  7. Maintain comprehensive logging and monitoring to detect anomalous activities indicative of exploitation attempts.
  8. Prepare incident response plans specific to CRM system compromises to enable rapid containment and recovery.

Description

An issue in BusinessNext CRMnext v.10.8.3.0 allows a remote attacker to execute arbitrary code via the comments input parameter.

References

Community reviews

Loading reviews…