critical CVSS 9.9

CVE-2024-51478·PHP vulnerability

YesWiki is a wiki system written in PHP. Prior to 4.4.5, the use of a weak cryptographic algorithm and a hard-coded salt to hash the password reset key allows it to be recovered and used to reset the password of any account. This issue is fixed in 4.4.5.

Severity
critical
Software
PHP
Fixed in
4.4.5
Published
2024-10-31

Affected versions

Until: 4.4.5

Fixed in: 4.4.5

How to fix this CVE

YesWiki installations running versions prior to 4.4.5 are vulnerable to password reset key recovery due to weak cryptographic hashing with a hardcoded salt. Immediately upgrade YesWiki to version 4.4.5 or later to replace the vulnerable password reset mechanism with a cryptographically secure implementation. After upgrading, invalidate all existing password reset tokens and require administrators to issue fresh password resets for affected users.

sudo dnf update php

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST /wakka.php?wiki=PasswordReset with repeated token generation attempts or GET requests containing base64-encoded predictable reset tokens matching the pattern ^[a-f0-9]{32}$ derived from weak hash algorithms

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch.

Implement rate limiting on password reset endpoints (/wakka.php?wiki=PasswordReset or similar) to block multiple reset attempts from the same IP within a short timeframe. Add WAF rules to detect and block requests containing suspicious password reset tokens with entropy patterns inconsistent with cryptographic randomness.

How to check if you are affected

  1. Step 1: Check YesWiki version by inspecting the release file: grep -r "VERSION" /path/to/yeswiki/includes/ | grep -i version
  2. Step 2: Search for password reset tokens in the YesWiki database: SELECT * FROM yeswiki_pages WHERE tag LIKE '%reset%' OR content LIKE '%token%' LIMIT 10;
  3. Step 3: Review web server access logs for unusual password reset requests: grep -i "reset\|pwd\|password" /var/log/apache2/access.log | grep POST
  4. Step 4: After upgrading to 4.4.5, verify the new cryptographic implementation is active by checking the commit hash in the installation: cd /path/to/yeswiki && git log --oneline | grep -i 'password\|hash\|crypto' | head -5

FAQ

What is CVE-2024-51478?

CVE-2024-51478 is a critical vulnerability in YesWiki that exploits weak password reset token generation. Attackers can predict and forge password reset keys due to the use of a hardcoded salt combined with weak hashing, allowing unauthorized account takeovers without requiring the original password.

Is CVE-2024-51478 being actively exploited?

No, CVE-2024-51478 is not currently listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits are available. However, the attack is trivial to execute once understood, making proactive patching critical.

What versions of YesWiki are affected by CVE-2024-51478?

All YesWiki versions prior to 4.4.5 are affected. Version 4.4.5 and later contain the security fix and should be deployed immediately.

How do I check if my server is vulnerable to CVE-2024-51478?

Determine your YesWiki version using: grep -r 'YESWIKI_VERSION' /path/to/yeswiki/includes/ or by checking the About page in the web interface. If the version is below 4.4.5, your installation is vulnerable.

Does Defensia detect CVE-2024-51478?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If YesWiki is installed on a monitored server, CVE-2024-51478 will appear in your dashboard with remediation steps.

Related PHP CVEs

CVE-2025-47916CVSS 10Invision Community 5.0.0 before 5.0.7 allows remote code execution via crafted template strings to themeeditor.php. The issue lies within the themeeditor controller (file: /applications/core/modules/front/system/themeeditor.php), where a protected method named customCss can be invoked by unauthenticated users. This method passes the value of the content parameter to the Theme::makeProcessFunction() method; hence it is evaluated by the template engine. Accordingly, this can be exploited by unauthenticated attackers to inject and execute arbitrary PHP code by providing crafted template strings.
CVE-2025-25174CVSS 10Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in beeteam368 BeeTeam368 Extensions beeteam368-extensions allows PHP Local File Inclusion.This issue affects BeeTeam368 Extensions: from n/a through <= 1.9.4.
CVE-2026-39337CVSS 10ChurchCRM is an open-source church management system. Prior to 7.1.0, critical pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The "$dbPassword" variable is not sanitized. This vulnerability exists due to an incomplete fix for CVE-2025-62521. This vulnerability is fixed in 7.1.0.
CVE-2025-46348CVSS 10YesWiki is a wiki system written in PHP. Prior to version 4.5.4, the request to commence a site backup can be performed and downloaded without authentication. The archives are created with a predictable filename, so a malicious user could create and download an archive without being authenticated. This could result in a malicious attacker making numerous requests to create archives and fill up the file system, or by downloading the archive which contains sensitive site information. This issue has been patched in version 4.5.4.
CVE-2025-62521CVSS 10ChurchCRM is an open-source church management system. Prior to version 5.21.0, a pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The vulnerability exists in `setup/routes/setup.php` where user input from the setup form is directly concatenated into a PHP configuration template without any validation or sanitization. Any parameter in the setup form can be used to inject PHP code that gets written to `Include/Config.php`, which is then executed on every page load. This is more severe than typical authenticated RCE vulnerabilities because it requires no credentials and affects the installation process that administrators must complete. Version 5.21.0 patches the issue.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-51478. Free for 1 server.

Get started free