# CVE-2024-34914: PHP Censor uses a weak hashing algorithm for the remember me key

> Weak hashing in php-censor allows attackers to brute-force remember keys and take over accounts of users who selected remember me.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-fqw7-839j-hvxj

## What is CVE-2024-34914?

CVE-2024-34914 is a medium-severity vulnerability in n/a, published on 14 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

php-censor v2.1.4 and fixed in v.2.1.5 was discovered to utilize a weak hashing algorithm for its remember_key value. This allows attackers to bruteforce to bruteforce the remember_key value to gain access to accounts that have checked "remember me" when logging in.

Weakness: CWE-328 (Use of Weak Hash)

## Which versions are affected by CVE-2024-34914?

4 open source packages ship an affected version, including php-censor/php-censor.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `php-censor/php-censor` | Packagist | All versions | 2.0.13 |
| `php-censor/php-censor` | Packagist | All versions | 2.0.13 |
| `php-censor/php-censor` | Packagist | From 2.1.0 | 2.1.5 |
| `php-censor/php-censor` | Packagist | From 2.1.0 | 2.1.5 |

## How do I fix CVE-2024-34914?

Upgrade php-censor/php-censor to a fixed version for your release line: 2.0.13 or 2.1.5.

## Is CVE-2024-34914 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34914 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34914 and fix it if it is affected.

What it is: CVE-2024-34914 is a medium-severity vulnerability in n/a, published on 14 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34914 exists.

Affected packages and fixed versions:
- php-censor/php-censor (Packagist): affected all versions; fixed in 2.0.13
- php-censor/php-censor (Packagist): affected all versions; fixed in 2.0.13
- php-censor/php-censor (Packagist): affected from 2.1.0; fixed in 2.1.5
- php-censor/php-censor (Packagist): affected from 2.1.0; fixed in 2.1.5

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-34914/ (Markdown: https://insights.sbomify.com/CVE-2024-34914/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-34914
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-34914
- OSV: https://osv.dev/vulnerability/CVE-2024-34914

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-34914/
Summaries are generated and may contain mistakes; the official description above is the record.