CVE-2025-69246: Raytha CMS does not have any brute force protection mechanism implemented

Q: How do I fix CVE-2025-69246?

raytha: upgrade to 1.4.6. Exact commands for each OS are on this page.

Q: Is CVE-2025-69246 being exploited?

CVE-2025-69246 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-69246 affect?

CVE-2025-69246 affects raytha. Severity is critical (CVSS 9.8). 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

Q: How urgent is CVE-2025-69246?

Priority 47/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2025-69246 is a critical-severity flaw (CVSS 9.8) affecting raytha. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 67%)
CISA exploited list	No
Weakness	CWE-307
Published	2026-03-16
Last modified	2026-06-17

Publisher (CNA): CERT.PL · Vendor: raytha

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-16 14:18 UTCPublished CVE record published
2026-06-17 10:00 UTCUpdated Record last modified

raytha raytha UPGRADE

Affected: < 1.4.6

Fixed in: 1.4.6

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy raytha || rpm -q raytha || raytha --version

2. UPGRADE to 1.4.6 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade raytha

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade raytha

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-69246?

raytha: upgrade to 1.4.6. Exact commands for each OS are on this page.

Is CVE-2025-69246 being exploited?

CVE-2025-69246 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-69246 affect?

CVE-2025-69246 affects raytha. Severity is critical (CVSS 9.8). 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

How urgent is CVE-2025-69246?

Priority 47/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-69245 MEDIUM 6.1 UPGRADE Raytha CMS is vulnerable to Reflected XSS via returnUrl parameter in logon functionality
CVE-2025-69243 MEDIUM 5.3 UPGRADE Raytha CMS is vulnerable to User Enumeration in password reset functionality
CVE-2025-69242 MEDIUM 6.1 UPGRADE Raytha CMS is vulnerable to reflected XSS via the backToListUrl parameter
CVE-2025-69241 MEDIUM 5.4 UPGRADE Raytha CMS is vulnerable to Stored XSS via FirstName and LastName parameters in profile editing functionality
CVE-2025-69240 HIGH 8.8 UPGRADE Raytha CMS allows an attacker to spoof `X-Forwarded-Host` or `Host` headers to attacker controlled domain

References

← Back to latest CVEs