Security Resilience

CVE-2023-26855

Crypto Weakness in Churchcrm 4.5.3

Public PoCCrypto Weakness
Published
04 April 2023
Modified
13 February 2025
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0073 53th percentile
Risk Priority 59 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-2023-26855 is a high-severity Use of Insufficiently Random Values (CWE-330) vulnerability in Churchcrm Churchcrm. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The hashing algorithm of ChurchCRM v4.5.3 utilizes a non-random salt value which allows attackers to use precomputed hash tables or dictionary attacks to crack the hashed passwords.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-25893Same product: Churchcrm Churchcrm
CVE-2025-68399Same product: Churchcrm Churchcrm
CVE-2026-26059Same product: Churchcrm Churchcrm
CVE-2026-39330Same product: Churchcrm Churchcrm
CVE-2026-39332Same product: Churchcrm Churchcrm
CVE-2023-27059Same product: Churchcrm Churchcrm
CVE-2026-35574Same product: Churchcrm Churchcrm
CVE-2026-39941Same product: Churchcrm Churchcrm
CVE-2026-35576Same product: Churchcrm Churchcrm
CVE-2023-24686Same product: Churchcrm Churchcrm

Affected Assets

churchcrm
churchcrm
4.5.3

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-330

Key generation under controlled management uses approved random-bit sources rather than insufficiently random values.

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.

blocks

Cryptographic controls require use of approved, sufficiently random values for keys and nonces.

blocks

Secure SDLC processes include verification steps that can catch insufficient randomness but do not directly specify RNG requirements.

prevents

Secure coding standards explicitly prohibit use of weak or predictable random number generators.

finds

Security testing can detect weak randomness but does not prescribe the control itself.

degrades

Secure authentication mechanisms depend on unpredictable values (nonces, salts, session tokens) to resist guessing.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

References