Cyber Resilience

CVE-2025-8117

Widzialni Pad Cms ≤ 1.2.1

Published
30 September 2025
Modified
26 November 2025
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/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.0025 17th percentile
Risk Priority 43 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-8117 is a high-severity Missing Initialization of Resource (CWE-909) vulnerability in Widzialni Pad Cms. Its CVSS base score is 8.7 (High).

Operationally, ranked at the 17th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

PAD CMS improperly initializes parameter used for password recovery, which allows to change password for any user that did not use reset password functionality. This issue affects all 3 templates: www, bip and www+bip. This product is End-Of-Life and producent…

more

will not publish patches for this vulnerability.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-7063Same product: Widzialni Pad Cms
CVE-2025-7065Same product: Widzialni Pad Cms
CVE-2025-8116Same product: Widzialni Pad Cms
CVE-2025-8118Same product: Widzialni Pad Cms
CVE-2025-8121Same product: Widzialni Pad Cms
CVE-2025-8119Same product: Widzialni Pad Cms
CVE-2025-8122Same product: Widzialni Pad Cms
CVE-2025-8120Same product: Widzialni Pad Cms
CVE-2025-38601Shared CWE-909
CVE-2025-54388Shared CWE-909

Affected Assets

widzialni
pad cms
≤ 1.2.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing initialization through static analysis or test cases.

Documented development standards and processes can mandate initialization of critical resources.

Security engineering principles can require explicit resource initialization during design and coding.

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.PS-06 mostly match
prevents

Secure SDLC practices directly require proper resource initialization as part of coding standards and verification.

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.

finds

Security testing can detect missing initialization defects before deployment.

prevents

Secure development life cycle mandates initialization of resources before use.

prevents

Application security requirements can specify resource initialization checks.

prevents

Secure architecture principles include proper resource lifecycle management.

prevents

Secure coding standards explicitly require initialization of variables and resources.

References