Skip to main content
CVE-2025-10329VulnerabilityPublished Updated

CVE-2025-10329: cdevroe unmark · Server-Side Request Forgery

Affects cdevroe unmarkSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Sep 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
cdevroe unmarkAffected
  • =1.9.0
  • =1.9.1
  • =1.9.2
  • =1.9.3
Fixed in–

AI-suggested

Given the absence of official patches, European organizations should implement immediate compensating controls. These include: 1) Restricting outbound HTTP/HTTPS requests from the unmark server to only trusted destinations using firewall rules or network segmentation to limit SSRF impact. 2) Employing web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the vulnerable 'url' parameter. 3) Conducting thorough input validation and sanitization on the 'url' parameter within unmark's codebase if possible, to reject or neutralize malicious inputs. 4) Monitoring logs for unusual outbound requests or access patterns indicative of SSRF exploitation attempts. 5) Isolating the unmark application in a hardened environment with minimal privileges and network access. 6) Planning for an upgrade or patch deployment once the vendor releases a fix or considering alternative software solutions if the vendor remains unresponsive. 7) Educating security teams about SSRF risks and detection techniques to improve incident response readiness.

Description

A vulnerability was detected in cdevroe unmark up to 1.9.3. This affects an unknown part of the file /application/controllers/Marks.php. The manipulation of the argument url results in server-side request forgery. The attack may be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

References

Community reviews

Loading reviews…