Cyber Resilience

CVE-2025-69246

Raytha ≤ 1.4.6

Published
16 March 2026
Modified
16 March 2026
Patch / advisory
View advisory
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/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:X
EPSS Score 0.0038 31th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2025-69246 is a medium-severity Improper Restriction of Excessive Authentication Attempts (CWE-307) vulnerability in Raytha Raytha. Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 31th 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-7 (Unsuccessful Logon Attempts) — 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-69246 is a critical vulnerability in Raytha CMS, published on 2026-03-16, stemming from the absence of any brute force protection mechanism on its login functionality. This allows attackers to send unlimited automated logon requests without lockout, throttling, or step-up challenges being triggered. Assigned CWE-307 and a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw affects Raytha CMS versions prior to 1.4.6.

Any remote attacker without privileges or user interaction can exploit this vulnerability over the network with low complexity. Successful exploitation enables brute-forcing login credentials, potentially granting full administrative access to the CMS, leading to high impacts on confidentiality, integrity, and availability through unauthorized data access, modification, or disruption.

The issue was addressed in Raytha CMS version 1.4.6. Additional details are available in advisories from CERT.pl at https://cert.pl/en/posts/2026/03/CVE-2025-69236 and the vendor site at https://raytha.com. Security practitioners should upgrade to the patched version and consider implementing supplementary brute force mitigations such as rate limiting or CAPTCHA on exposed instances.

OWASP Top 10 for Web (2025)

A07:2025 Authentication Failures

EU & UK References

Vulnerability Data

Raytha CMS does not have any brute force protection mechanism implemented. It allows an attacker to send multiple automated logon requests without triggering lockout, throttling, or step-up challenges. This issue was fixed in version 1.4.6.

CWE(s)
CWE-307

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
T1110.001 Password Guessing Credential Access
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
attack.mitre.org →
T1110.003 Password Spraying Credential Access
Adversaries may use a single or small list of commonly used passwords against many different accounts to attempt to acquire valid account credentials.
attack.mitre.org →
T1110.004 Credential Stuffing Credential Access
Adversaries may use credentials obtained from breach dumps of unrelated accounts to gain access to target accounts through credential overlap.
attack.mitre.org →
T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-69243Same product: Raytha Raytha
CVE-2025-69240Same product: Raytha Raytha
CVE-2025-69238Same product: Raytha Raytha
CVE-2025-69241Same product: Raytha Raytha
CVE-2025-69236Same product: Raytha Raytha
CVE-2025-69237Same product: Raytha Raytha
CVE-2025-69245Same product: Raytha Raytha
CVE-2025-69242Same product: Raytha Raytha
CVE-2025-15540Same product: Raytha Raytha
CVE-2025-69239Same product: Raytha Raytha

Affected Assets

raytha
raytha
≤ 1.4.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

AC-7 Unsuccessful Logon Attempts good match

AC-7 directly enforces limits on consecutive failed logons, structurally blocking brute-force exploitation of the weakness.

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.

PR.AA-03 mostly match
prevents

Authentication enforcement directly includes lockout, throttling, and MFA policies that prevent brute-force attempts.

DE.CM-03 partial match
prevents

Behavioral monitoring of authentication activity can detect excessive failed attempts after they occur.

PR.PS-04 partial match
prevents

Generating auth logs enables later detection or forensics but does not itself restrict attempts.

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.

A.8.5 Secure authentication partial match
prevents

CAPTCHA, account lock-out after repeated failures, and alerts on excessive attempts directly stop automated brute-force guessing of credentials.

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).

RHEL 7 (2 rules)
  • V-204427 The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 15 minutes after three unsuccessful logon attempts within a 15-minute timeframe. prevents CWE-307
  • V-204428 The Red Hat Enterprise Linux operating system must lock the associated account after three unsuccessful root logon attempts are made within a 15-minute period. prevents CWE-307

References