# CVE-2026-118377: mews/pos through 2.0.0 Missing Hash Verification in 3D Pay and 3D Host Callbacks


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-qfwr-rmpq-mvmx

## What is CVE-2026-118377?

CVE-2026-118377 is a high-severity vulnerability in mewebstudio pos, published on 28 Oct 2026. 

### Official description

mews/pos through 2.0.0 contains an insufficient verification of data authenticity vulnerability that allows unauthenticated attackers to forge payment results by submitting unverified callbacks. GarantiPos, PayForPos and InterPos 3D Pay and 3D Host handlers skip check3DHash(), letting attackers post tampered status, amount or order ID fields to complete orders without paying.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-118377?


## How do I fix CVE-2026-118377?

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

## Is CVE-2026-118377 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118377 and fix it if it is affected.

What it is: CVE-2026-118377 is a high-severity vulnerability in mewebstudio pos, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118377 in the wild and no public exploit code.

Affected product: mewebstudio pos. 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-2026-118377/ (Markdown: https://insights.sbomify.com/CVE-2026-118377/index.md)
```

## Sources

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

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