# CVE-2018-14596: Denial of service in n/a

> Remote attackers can cause denial of service in wancms by sending large values for font size, width, and height in the verification code URI.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v7xm-5488-frx3

## What is CVE-2018-14596?

CVE-2018-14596 is a high-severity denial of service vulnerability in n/a, published on 25 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

wancms 1.0 through 5.0 allows remote attackers to cause a denial of service (resource consumption) via a checkcode (aka verification code) URI in which the values of font_size, width, and height are large numbers.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Wancms Wancms.

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

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

## Is CVE-2018-14596 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14596 is a high-severity denial of service vulnerability in n/a, published on 25 Jul 2018. 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-14596 in the wild and no public exploit code.

Affected product: n/a. 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-14596/ (Markdown: https://insights.sbomify.com/CVE-2018-14596/index.md)
```

## Sources

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

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