CVE-2026-10715
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 · uneditedCamaleon CMS 2.9.2 contains an improper authorization vulnerability in the administrator draft autosave endpoint. A low-privileged authenticated user can send an arbitrary post_id to POST /admin/post_type/<POST_TYPE_ID>/drafts and overwrite the draft associated with another user's post.
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 confidenceCamaleon CMS 2.9.2 has an Insecure Direct Object Reference (IDOR) vulnerability in the draft autosave endpoint. The application allows any authenticated user to specify an arbitrary post_id in the POST request to /admin/post_type/<POST_TYPE_ID>/drafts without verifying ownership, enabling a low-privileged user to overwrite drafts belonging to other users.
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
- Low
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 if Camaleon CMS is installedLook for Camaleon CMS application files in the web root, or check the Gemfile for 'camaleon_cms' gem, or examine the Rails application's gem dependencies.Affected if Camaleon CMS is present in the environment
-
Check the installed Camaleon CMS versionRun 'gem list camaleon_cms' or check the Gemfile.lock for the camaleon_cms version number.Affected if The installed version is 2.9.2 or falls within the affected range without patches
-
Verify the draft autosave endpoint existsCheck if the route /admin/post_type/:post_type_id/drafts is defined in the application's routes (run 'rake routes' or inspect config/routes.rb).Affected if The drafts endpoint is defined and accessible at /admin/post_type/<POST_TYPE_ID>/drafts
-
Confirm authentication is required for the endpointAttempt to access the drafts endpoint without credentials; verify the application requires authentication.Affected if The endpoint requires authentication but does not verify post ownership
-
Test for IDOR vulnerability in draft accessLog in as a low-privileged user, create a draft for a post, then attempt to modify a draft belonging to a different user by specifying another user's post_id in the POST request to /admin/post_type/<POST_TYPE_ID>/drafts.Affected if An authenticated user can successfully overwrite drafts belonging to other users by manipulating the post_id parameter
A user is affected if Camaleon CMS version 2.9.2 is installed and the application allows any authenticated user to modify drafts for posts they do not own via the /admin/post_type/<POST_TYPE_ID>/drafts 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 proper authorization checks to verify the authenticated user owns the post_id before allowing draft modifications. Additionally, enforce that users can only access drafts for posts they created or have permission to edit.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10715 — 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-2026-10715 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