# CVE-2018-25422: MOGG web simulator Script All Version SQL Injection via play.php

> Unauthenticated attackers can execute arbitrary SQL commands via the id parameter in play.php to extract sensitive database information.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/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:** 30 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-m4wp-hx6h-3pvv

## What is CVE-2018-25422?

CVE-2018-25422 is a high-severity SQL injection vulnerability in spider312 MOGG web simulator Script, published on 30 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MOGG web simulator Script contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL commands by injecting malicious code through the id parameter. Attackers can send GET requests to play.php with crafted SQL payloads in the id parameter to extract sensitive database information including usernames and other data.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2018-25422?


## How do I fix CVE-2018-25422?

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

## Is CVE-2018-25422 being exploited?

There is no known exploitation of CVE-2018-25422 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25422 and fix it if it is affected.

What it is: CVE-2018-25422 is a high-severity SQL injection vulnerability in spider312 MOGG web simulator Script, published on 30 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-25422 in the wild and no public exploit code.

Affected product: spider312 MOGG web simulator Script. 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-2018-25422/ (Markdown: https://insights.sbomify.com/CVE-2018-25422/index.md)
```

## Sources

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

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