CVE-2024-54434
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in BenJemin phZoom phzoom allows Stored XSS.This issue affects phZoom: from n/a through <= 1.2.92.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA CSRF vulnerability in BenJemin phZoom versions up to 1.2.92 allows attackers to craft malicious requests that result in Stored XSS. Attackers can exploit the lack of CSRF protection to force authenticated users to execute unintended actions that inject persistent malicious scripts into the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify phZoom installation and versionSearch for phZoom files in your web root (commonly in /phzoom/, /include/phzoom/, or as part of a theme/plugin). Check for version.php, readme.txt, or the main phZoom script header for version number.Affected if The installed version is 1.2.92 or lower, or if no version is discernible but the product is present.
-
Confirm authentication is in useReview your application to determine if phZoom is integrated with an authenticated user system (loginrequired, session-based auth, or user accounts).Affected if phZoom is accessible to authenticated users or is embedded in an application with user authentication.
-
Inspect state-changing endpoints for CSRF protectionLocate endpoints in phZoom that accept user input and modify data (such as settings, image metadata, or configuration savers). Review the source code for anti-CSRF token validation or SameSite cookie enforcement on POST/PUT requests.Affected if State-changing actions lack CSRF token validation or do not verify request origin.
-
Examine input handling for Stored XSS vectorsTrace user-supplied inputs (URL parameters, form fields, file names) that are stored and later rendered. Check if these inputs are validated and output-encoded before storage or display.Affected if User input is stored without proper validation or output encoding, allowing script injection.
Your environment is affected if phZoom version 1.2.92 or lower is installed, the application uses authenticated sessions, and state-changing endpoints lack CSRF protection while accepting unsanitized user input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens on all state-changing endpoints and apply proper input validation with context-aware output encoding to prevent the stored XSS. Additionally, configure SameSite cookie attributes.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54434 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54434 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data