# CVE-2018-25307: SysGauge Pro 4.6.12 Local Buffer Overflow SEH

> Local attackers can execute arbitrary code by exploiting a buffer overflow in the registration key field of SysGauge Pro.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-q23w-prg2-248g

## What is CVE-2018-25307?

CVE-2018-25307 is a high-severity memory corruption vulnerability in SysGauge Pro, published on 29 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SysGauge Pro 4.6.12 contains a local buffer overflow vulnerability in the Register function that allows local attackers to overwrite the structured exception handler by supplying a crafted unlock key. Attackers can inject shellcode through the Unlock Key field during registration to execute arbitrary code with application privileges.

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

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


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

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

## Is CVE-2018-25307 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25307 is a high-severity memory corruption vulnerability in SysGauge Pro, published on 29 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-25307 exists.

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

## Sources

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

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