# CVE-2025-6397: XSS in Ankara Hosting's web site

> Ankara Hosting's Website Design Software allows reflected XSS, enabling attackers to execute scripts in user browsers.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 3 Feb 2026
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-69rq-p84j-w9cp

## What is CVE-2025-6397?

CVE-2025-6397 is a high-severity cross-site scripting vulnerability in Ankara Hosting Website Design Website Software, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Ankara Hosting Website Design Website Software allows Reflected XSS.

This issue affects Website Software: through 03022026. 

NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-6397?


## How do I fix CVE-2025-6397?

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

## Is CVE-2025-6397 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6397 and fix it if it is affected.

What it is: CVE-2025-6397 is a high-severity cross-site scripting vulnerability in Ankara Hosting Website Design Website Software, published on 3 Feb 2026. 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-2025-6397 in the wild and no public exploit code.

Affected product: Ankara Hosting Website Design Website Software. 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-2025-6397/ (Markdown: https://insights.sbomify.com/CVE-2025-6397/index.md)
```

## Sources

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

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