CVE-2024-26351
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 · uneditedflusity-CMS v2.33 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /core/tools/update_place.php
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 · high confidenceflusity-CMS v2.33 contains a Cross-Site Request Forgery (CSRF) vulnerability in the /core/tools/update_place.php component. This allows attackers to trick authenticated users into submitting unintended requests to update place data, as the affected endpoint lacks proper anti-CSRF token validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.33CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/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.
-
Confirm flusity-CMS versionLocate the version identifier in the flusity-CMS installation (typically in a configuration file, README, or admin dashboard about section) and verify it is exactly version 2.33Affected if The installed version is exactly 2.33
-
Verify update_place.php existsCheck if the file /core/tools/update_place.php exists in the web root or application directory of the flusity-CMS installationAffected if The file /core/tools/update_place.php is present in the installation
-
Inspect anti-CSRF token validation in update_place.phpOpen /core/tools/update_place.php and examine the code for presence of anti-CSRF token validation (look for token checks, synchronizer token pattern, or similar validation logic before processing the update request)Affected if The update_place.php endpoint lacks proper anti-CSRF token validation logic in its code
-
Check SameSite cookie configurationReview the application cookie configuration or session settings to determine if SameSite cookie attributes are enforced on session cookiesAffected if SameSite cookie attributes are not properly configured (this is a defense-in-depth measure whose absence increases CSRF risk)
The environment is affected if flusity-CMS version 2.33 is installed, the update_place.php endpoint exists, and the code lacks anti-CSRF token validation on that endpoint.
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 (synchronizer token pattern) on the update_place.php endpoint and validate them server-side. Additionally, enforce SameSite cookie attributes and validate Origin/Referer headers as defense-in-depth measures.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26351 — 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-26351 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