CVE-2025-69240
Raytha ≤ 1.4.6
Raw vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-69240 is a high-severity Use of Less Trusted Source (CWE-348) vulnerability in Raytha Raytha. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-69240 is a vulnerability in Raytha CMS that enables attackers to spoof the `X-Forwarded-Host` or `Host` headers to an attacker-controlled domain. Published on 2026-03-16, it stems from improper validation of these headers (CWE-348), allowing manipulation of password reset links generated by the server. The issue affects Raytha CMS versions prior to 1.4.6 and carries a CVSS v3.1 score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), highlighting its high severity due to network accessibility, low attack complexity, and significant impacts on confidentiality, integrity, and availability.
An attacker who knows a victim's email address can exploit this by spoofing the headers during a request that triggers a password reset email. The server then sends the victim an email with a reset link pointing to the attacker's domain. Upon clicking the link, the victim's browser issues a request to the attacker's domain, embedding the reset token in the path, which the attacker captures. This grants the attacker the ability to reset the victim's password and fully compromise their account.
The vulnerability was addressed in Raytha CMS version 1.4.6. Additional details are available in advisories from CERT.pl (https://cert.pl/en/posts/2026/03/CVE-2025-69236) and the Raytha website (https://raytha.com). Security practitioners should upgrade to the patched version and review configurations for header validation in similar CMS platforms.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-208707
- 🇵🇱 CERT-PL: cert.pl
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 7 hardening rules · 4 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Provenance tracking supplies the information needed to distinguish and prefer more-trusted sources, reducing the chance that a weaker source is chosen.
Information flow enforcement can require that data or decisions are taken only from explicitly approved, higher-trust sources rather than less-verified ones.
Device identification and authentication forces verification of the source before any data it supplies is used, eliminating reliance on unauthenticated inputs.
Boundary protection monitors and filters traffic at external interfaces, structurally limiting the ability to accept data from less-trusted external sources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Explicit authenticity/integrity checks before use directly reduce selection of a less-trusted source.
Correlating multiple sources can surface discrepancies that discourage reliance on the less-trusted one.
Protecting data-in-transit integrity helps ensure the more-trusted source is the one whose data is accepted.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure architecture principles include trusted input channels and source verification mechanisms.
Security testing can detect and prevent acceptance of data from less-trusted sources during development.
Network security controls can enforce trusted data paths and source validation, reducing reliance on unverified inputs.
Secure network services include source validation and integrity checks that help prevent acceptance of data from less-trusted origins.
Application security requirements can mandate trusted data sources and input validation, directly addressing the weakness.
Secure coding practices can enforce checks that prefer or validate the more trusted data source.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-348
Oracle Linux 9 (1 rule)
- V-271525 OL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-348
RHEL 7 (1 rule)
- V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-348