# CVE-2026-124506: Dianping CAT Report hourlyReport.tag Model.getDomain cross site scripting


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-h87p-q65v-qqrr

## What is CVE-2026-124506?

CVE-2026-124506 is a medium-severity vulnerability in Dianping CAT, published on 9 Nov 2026. 

### Official description

A vulnerability has been found in Dianping CAT 3.0.0/3.1.0/4.0-RC1. This vulnerability affects the function Model.getDomain of the file WEB-INF/tags/hourlyReport.tag of the component Report Handler. The manipulation of the argument domain leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-124506 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124506 is a medium-severity vulnerability in Dianping CAT, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124506 in the wild and no public exploit code.

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

## Sources

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

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