CVE-2025-8118: PAD CMS implements weak client-side brute-force protection by utilizing two cookies: login_count and
Source GCVE Database
Not known to be exploited · CVSS 6.9 Medium · end of life, no fix coming : replace or isolate affected systems; no fix will be released.
Data as of 19 Nov 2026, 02:33 UTC
- Patch
- None coming – the product is end of life
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
No fix will be released: the affected product is end of life. Replace it, or isolate it from untrusted networks until you can.
AI-suggested
Since PAD CMS is End-Of-Life and no patches will be released, users should consider migrating to a supported CMS product. As a workaround, administrators could implement server-side brute-force protections or use external security controls such as web application firewalls to limit login attempts. Relying solely on client-side controls for security is ineffective and should be avoided.
Description
PAD CMS uses weak client-side brute-force protection relying on two cookies, login_count and login_timeout, without server-side tracking. This allows attackers to bypass brute-force protections by resetting these cookies. The vulnerability affects all three templates: www, bip, and www+bip. The product is End-Of-Life and no patches will be provided.