CVE-2024-51687
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 Platform.ly Platform.ly Official platformly allows Stored XSS.This issue affects Platform.ly Official: from n/a through <= 1.1.3.
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 confidenceCSRF vulnerability in Platform.ly <= 1.1.3 allows attackers to craft malicious requests that cause authenticated users to unknowingly inject stored XSS payloads into the application. The lack of CSRF protection on sensitive endpoints enables attackers to exploit the application via social engineering.
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 installed Platform.ly versionCheck your application files, package.json, composer.json, or the admin dashboard for the current Platform.ly version number. Compare it to the affected range: version 1.1.3 or lower.Affected if The installed version is 1.1.3 or any lower version number.
-
Locate state-changing endpointsReview application source code for endpoints that modify data: user profile updates, content creation, settings changes, or any POST/PUT/DELETE request handlers.Affected if Sensitive endpoints exist that perform state-changing operations.
-
Inspect forms and AJAX requests for CSRF tokensExamine HTML forms and JavaScript AJAX calls for the presence of CSRF synchronizer tokens (typically hidden input fields named _token, csrf_token, or similar, or custom headers). Check if the server validates these tokens on submission.Affected if Forms and API requests lack CSRF token generation and validation.
-
Verify stored XSS injection pointTest whether data submitted through the unprotected endpoints is stored in the database and rendered without proper context-aware encoding when viewed by other users.Affected if User-submitted data is rendered in the browser without output encoding, allowing script injection.
You are affected if Platform.ly version is 1.1.3 or lower AND sensitive endpoints lack CSRF token protection, allowing attackers to force authenticated users to inject stored XSS payloads.
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 CSRF synchronizer token pattern on all state-changing operations and apply robust input validation with context-aware output encoding to prevent stored XSS.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51687 — 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-51687 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