Read the docs
TI-2025-42699 Aliases CVE-2025-69246GHSA-ffgf-qg52-hgm3

Lack of bruteforce protection in Raytha CMS

Priority LOW 37CWE-307Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
Low · Low · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-307.

Summary

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 it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00396 34th percentileScored 2026-11-07
Fix Fixed Raytha (Raytha): 1.4.6

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
RaythaRaythabefore 1.4.61.4.6Patch availableCNA
  • Raytha VendorRaytha Affected before 1.4.6 Fixed in 1.4.6 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:raytha:raytha:*:*:*:*:*:*:*:*before 1.4.6VulnerableRaytha
  • cpe:2.3:a:raytha:raytha:*:*:*:*:*:*:*:* Versions before 1.4.6 Vulnerable ·Raytha

Remediation

  • Fix · CNA Raytha (Raytha) Fixed in 1.4.6

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Raytha 1.4.6

    10 records Highest priority Priority MEDIUM 1 MEDIUM, 9 LOW

    Other records, highest priority first

Timeline

  1. 2026-10-02 Threatist record created from CVE-2025-69246
  2. 2026-10-03 Alias added: GHSA-ffgf-qg52-hgm3

References

See all 10 →

Sources