{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-69246 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-69246 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69246 is a medium-severity vulnerability in Raytha, published on 16 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-69246 and fix it if it is affected.\n\nWhat it is: CVE-2025-69246 is a medium-severity vulnerability in Raytha, published on 16 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-69246 in the wild and no public exploit code.\n\nAffected product: Raytha. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-69246/ (Markdown: https://insights.sbomify.com/CVE-2025-69246/index.md)","id":"CVE-2025-69246","markdown":"https://insights.sbomify.com/CVE-2025-69246/index.md","name":"CVE-2025-69246","record":{"aliases":["GHSA-ffgf-qg52-hgm3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Raytha CMS","requires_auth":"none","summary":"Attackers can perform brute-force attacks on Raytha CMS due to missing lockout mechanisms, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[{"product":"raytha","vendor":"raytha"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"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.\n\nThis issue was fixed in version 1.4.6.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Lack of bruteforce protection in Raytha CMS","id":"CVE-2025-69246","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"free5GC has Heap Buffer Overflow in UPF Leading to Denial of Service","id":"CVE-2025-69247"},"packages":[],"prev":{"headline":"Reflected XSS in Raytha CMS","id":"CVE-2025-69245"},"products":["Raytha"],"published":"2026-03-16","related":[{"cvss_score":8.6,"headline":"Authenticated RCE in Raytha CMS","id":"CVE-2025-15540","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":7.5,"headline":"Header Poisoning in Raytha CMS","id":"CVE-2025-69240","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":6.9,"headline":"Cross-Site Request Forgery in Raytha CMS","id":"CVE-2025-69238","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":6.9,"headline":"User enumeration in Raytha CMS","id":"CVE-2025-69243","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":5.3,"headline":"Stored XSS in Raytha CMS","id":"CVE-2025-69241","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":5.1,"headline":"Stored XSS in Raytha CMS","id":"CVE-2025-69236","kev_date_added":null,"published":"2026-03-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-16","vendors":["Raytha"]},"summary":"Attackers can perform brute-force attacks on Raytha CMS due to missing lockout mechanisms, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2025-69246/"}