# CVE-2025-34102: CryptoLog Unauthenticated RCE via SQL Injection and Command Injection

> Unauthenticated attackers can achieve remote code execution by chaining SQL injection for authentication bypass with command injection in the discontinued CryptoLog PHP application.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-8mgf-p582-j48h

## What is CVE-2025-34102?

CVE-2025-34102 is a critical SQL injection vulnerability in Crypttech CryptoLog, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote code execution vulnerability exists in CryptoLog (PHP version, discontinued since 2009) due to a chained exploitation of SQL injection and command injection vulnerabilities. An unauthenticated attacker can gain shell access as the web server user by first exploiting a SQL injection flaw in login.php to bypass authentication, followed by command injection in logshares_ajax.php to execute arbitrary operating system commands.

The login bypass is achieved by submitting crafted SQL via the user POST parameter. Once authenticated, the attacker can abuse the lsid POST parameter in the logshares_ajax.php endpoint to inject and execute a command using $(...) syntax, resulting in code execution under the web context.

This exploitation path does not exist in the ASP.NET version of CryptoLog released since 2009.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-306 (Missing Authentication for Critical Functionality), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-34102?


## How do I fix CVE-2025-34102?

No fix has been published for CVE-2025-34102 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-34102 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34102 exists.

Public exploit code:

- Crypttech CryptoLog Remote Code Execution (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-34102 and fix it if it is affected.

What it is: CVE-2025-34102 is a critical SQL injection vulnerability in Crypttech CryptoLog, published on 10 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-34102 exists.

Affected product: Crypttech CryptoLog. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-34102/ (Markdown: https://insights.sbomify.com/CVE-2025-34102/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-34102
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-34102
- OSV: https://osv.dev/vulnerability/CVE-2025-34102

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-34102/
Summaries are generated and may contain mistakes; the official description above is the record.