CVE-2024-51649
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 Patrick Lumumba Mobilize mobilize allows Stored XSS.This issue affects Mobilize: from n/a through <= 3.0.7.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in Mobilize platform allows authenticated attackers to inject malicious scripts through forged requests, resulting in Stored XSS. The vulnerability exists in versions through 3.0.7, where the application fails to properly validate CSRF tokens and sanitize user-supplied input before persistence.
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 Mobilize platform installation and versionLocate the Mobilize platform application files and check the version identifier in the application metadata, configuration files, or about/version page. Common locations include the main application directory, version manifest, or admin interface.Affected if The installed version is 3.0.7 or any earlier version of the Mobilize platform.
-
Verify CSRF protection on state-changing operationsExamine the application's request handling for forms or API endpoints that perform state changes (such as creating/updating user profiles, posts, or comments). Inspect whether anti-CSRF tokens are generated, required, and validated for each request.Affected if State-changing operations do not require or validate CSRF tokens, allowing forged requests to be processed.
-
Inspect stored content handlingReview how user-supplied input is processed before being saved to the database. Check if the application applies input validation or sanitization to content that will be persistently stored.Affected if User-supplied input is stored without sanitization or context-aware encoding, allowing malicious scripts to be persisted.
-
Check output encoding on rendered contentExamine how stored content is rendered back to users. Verify that output encoding is applied based on context (HTML, JavaScript, URL, etc.) to prevent XSS execution.Affected if Stored content is rendered without proper context-aware encoding, enabling stored XSS to execute in user browsers.
You are affected if running Mobilize platform version 3.0.7 or earlier AND the application lacks CSRF token validation on operations that store user content AND stored content is rendered without proper sanitization or encoding.
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 for state-changing operations and apply proper input validation with context-aware output encoding to prevent XSS execution. Upgrade to a patched version if available.
- Consultation4.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51649 — 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-51649 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