CVE-2025-6095
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 · uneditedA vulnerability, which was classified as critical, was found in codesiddhant Jasmin Ransomware 1.0.1. Affected is an unknown function of the file /checklogin.php. The manipulation of the argument username/password leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 · high confidenceSQL injection vulnerability in /checklogin.php of Jasmin Ransomware 1.0.1 allows remote attackers to manipulate username/password arguments to inject malicious SQL queries, potentially enabling unauthorized database access, data exfiltration, or further system compromise.
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= 1.0.1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Jasmin Ransomware versionLocate and read the version file or check the main script/header for version identification markers showing '1.0.1'Affected if The installed version is Jasmin Ransomware 1.0.1
-
Verify checklogin.php existsSearch the web root or application directory for the file /checklogin.phpAffected if The file checklogin.php exists in the application root
-
Confirm login page is accessibleAttempt to access the login page or check for routes serving checklogin.php functionalityAffected if The login functionality at checklogin.php is exposed and accessible via HTTP(s)
-
Check for dynamic SQL patternsIf source code is accessible, examine checklogin.php for unsanitized $_POST or $_GET usage on username/password parameters passed directly to SQL queriesAffected if The code contains direct concatenation of username/password inputs into SQL queries without prepared statements or parameterization
A system is affected if it runs Jasmin Ransomware version 1.0.1 with the checklogin.php file accessible and containing dynamic SQL query construction using unsanitized username/password inputs.
Generated from the published advisory. Verify against your own configuration.
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 · scopedReplace dynamic SQL queries in /checklogin.php with parameterized queries/prepared statements; implement strict input validation on username/password fields; apply principle of least privilege to database credentials.
- Do not deploy or use Jasmin Ransomware software - it is malware designed to encrypt files and extort victims
- If this software is found in your environment, treat it as a security incident and conduct a full forensic investigation
- Remove all instances of this software immediately
- Scan affected systems for indicators of compromise
- Restore from known-good backups if systems were compromised
- Report the presence of this malware to appropriate authorities (e.g., CISA, law enforcement)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-6095 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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