# CVE-2018-25294: CEWE Photoshow 6.3.4 Buffer Overflow Denial of Service

> Attackers can crash the CEWE Photoshow application by submitting oversized input to the login dialog fields.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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:** 26 Apr 2026
- **Updated:** 27 Apr 2026
- **Also known as:** GHSA-rhqc-mh74-4jfx

## What is CVE-2018-25294?

CVE-2018-25294 is a high-severity memory corruption vulnerability in Cewe-Photoworld CEWE Photoshow, published on 26 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CEWE Photoshow 6.3.4 contains a buffer overflow vulnerability in the login dialog that allows attackers to crash the application by submitting oversized input. Attackers can inject 4000 bytes of data into the email address and password fields to trigger a denial of service condition.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2018-25294 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25294 is a high-severity memory corruption vulnerability in Cewe-Photoworld CEWE Photoshow, published on 26 Apr 2026. 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-2018-25294 exists.

Affected product: Cewe-Photoworld CEWE Photoshow. 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-25294/ (Markdown: https://insights.sbomify.com/CVE-2018-25294/index.md)
```

## Sources

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

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