# CVE-2025-69240: Header Poisoning in Raytha CMS

> Attackers can spoof headers to send password reset links to their domain, capturing tokens to take over victim accounts.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-qj5q-vmr2-gmq3

## What is CVE-2025-69240?

CVE-2025-69240 is a high-severity vulnerability in Raytha, published on 16 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Raytha CMS allows an attacker to spoof `X-Forwarded-Host` or `Host` headers to attacker controlled domain. The attacker (who knows the victim's email address) can force the server to send an email with password reset link pointing to the domain from spoofed header. When victim clicks the link, browser sends request to the attacker’s domain with the token in the path allowing the attacker to capture the token. This allows the attacker to reset victim's password and take over the victim's account.

This issue was fixed in version 1.4.6.

Weakness: CWE-348 (Use of Less Trusted Source)

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

It affects 1 product.


Products: Raytha Raytha.

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

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

## Is CVE-2025-69240 being exploited?

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

## Other vulnerabilities in Raytha

- [CVE-2025-15540](https://insights.sbomify.com/CVE-2025-15540/): Authenticated RCE in Raytha CMS (high 8.6)
- [CVE-2025-69238](https://insights.sbomify.com/CVE-2025-69238/): Cross-Site Request Forgery in Raytha CMS (medium 6.9)
- [CVE-2025-69243](https://insights.sbomify.com/CVE-2025-69243/): User enumeration in Raytha CMS (medium 6.9)
- [CVE-2025-69246](https://insights.sbomify.com/CVE-2025-69246/): Lack of bruteforce protection in Raytha CMS (medium 6.9)
- [CVE-2025-69241](https://insights.sbomify.com/CVE-2025-69241/): Stored XSS in Raytha CMS (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69240 is a high-severity vulnerability in Raytha, published on 16 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-69240 in the wild and no public exploit code.

Affected product: Raytha. 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-69240/ (Markdown: https://insights.sbomify.com/CVE-2025-69240/index.md)
```

## Sources

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

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