Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as category manager for one post type
-
ExploitCraft update/destroy request with foreign category ID
-
ExecutionServer resolves category via unscoped global lookup
-
ImpactRename or delete unauthorized categories
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires an authenticated Camaleon CMS user who holds category-management permission for at least one post type (role meta such as _post_type_<id> => {'categories' => 1}); the attacker then supplies their own authorized post_type_id in the route while referencing a category ID owned by a different post type. Exploitation is limited by this authentication/authorization prerequisite (PR:L - a low-privilege but non-anonymous account is needed), affects only Camaleon CMS versions before 2.9.2, and impact is confined to renaming or deleting category objects within the same site; it does not grant data disclosure or code execution. The flaw stems from Admin::CategoriesController resolving the category via a global ID lookup rather than scoping it to the authorized post type. |
| Impact | This is a medium-severity (CVSS 4.0 base 5.3) authorization flaw whose real-world risk is moderate and bounded. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L) confirms network reach and low attack complexity but requires an already-authenticated low-privilege user (PR:L), and impact is limited to integrity (category rename) and availability (category deletion) with no confidentiality exposure (VC:N). The vendor-assigned CWE-639 and the patch diff confirm this is an IDOR/broken-object-authorization issue, not a pre-auth compromise - the attacker must already hold category-management rights for at least one post type. No EPSS score is provided in the input, so probability-of-exploitation cannot be quantified. The vulnerability is NOT on the CISA KEV list and there is no confirmed standalone public exploit; however, the merged fix PR #1148 ships a regression test that discloses the exact malicious request pattern, lowering the bar to reproduce it. The vuln.today priority of 'this_month' aligns with these signals: a genuine authorization bug worth patching on a normal monthly cadence rather than an emergency. Note one tension for triage: the 'Authentication Bypass' tag is imprecise - this is an authorization/IDOR issue affecting already-authenticated users, not an authentication bypass. |
| Exploit ScenarioDerived | An attacker holds a valid Camaleon CMS account with category-management permission for one post type (e.g., a contributor role). They send a PATCH or DELETE request to /admin/post_type/<their_authorized_post_type_id>/categories/<arbitrary_category_id>, pairing their authorized post_type_id with a category ID belonging to a different post type, to rename or delete categories they were never granted access to. No standalone weaponized exploit is published, but the regression test in fix PR #1148 demonstrates the precise request needed to trigger it. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 02, 2026
Category-management authorization bypass in Camaleon CMS before 2.9.2 lets an authenticated low-privileged user rename or delete categories belonging to a different post type by pairing their own authorized post_type_id with an arbitrary category ID in update or destroy requests. The flaw is an insecure direct object reference (CWE-639) in Admin::CategoriesController with medium severity impact limited to integrity and availability of category objects; it does not disclose data or enable code execution. Vendor-released patch 2.9.2 is available, and no public exploit code was identified at time of analysis.
RemediationAI
Upgrade to Camaleon CMS 2.9.2 or later; the vendor-released patch is 2.9.2. Apply the upstream fix from PR 1148 and commit fa465e994bcbf4e7be4605853c204b73dea7bbc5, and refer to the 2.9.2 release note and the VulnCheck advisory at https://www.vulncheck.com/advisories/camaleon-cms-before-2.9.2-idor-via-admin-categoriescontroller. The fix scopes the category lookup to the authorized post type and returns 404 when the category is not found. If upgrading immediately is not possible, restrict the category-management permission, such as the _post_type_<id> categories role meta, to accounts trusted to manage every category in the site or remove it from lower-privileged roles; this reduces exposure but does not replace the scoped lookup fix and may limit legitimate delegated category administration.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Camaleon CMS is a Ruby on Rails content management system. The affected code is the admin categories controller, which resolves the target category through a global lookup, CamaleonCms::Category.find_by_id(params[:id]), instead of constraining the lookup to the post type the current user is authorized to manage. This is an authorization bypass through a user-controlled key (CWE-639): a user with category-management permission for one post type can supply their valid post_type_id in the route while referencing a category ID owned by another post type. The supplied patch changes the lookup to @post_type.categories.find_by_id(params[:id]) and renders 404 when no scoped category is found, binding object access to the authorized post type. The CVSS 4.0 vector AV:N/AC:L/AT:N/PR:L/UI:N indicates a network-reachable issue requiring a low-privileged authenticated account, with low integrity and availability impact and no confidentiality impact. The CPE cpe:2.3:a:owen2345:camaleon_cms:*:*:*:*:*:*:*:* identifies the affected product family, and the supplied source evidence places the vulnerable controller in version 2.9.1.
Know when Camaleon Cms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
Remote authenticated low-privilege user (PR:L) with a simple request (AC:L); unauthorized category rename gives I:L and deletion gives A:L, with no data disclosure (C:N) and unchanged scope.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Camaleon CMS before 2.9.2 contains an insecure direct object reference vulnerability in Admin::CategoriesController that allows authenticated users to modify unauthorized categories by referencing arbitrary category IDs. Users authorized for one post type can send update or destroy requests pairing another category ID with their authorized post_type_id to rename or delete categories.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Camaleon Cms
View allCamaleon CMS is a dynamic and advanced content management system based on Ruby on Rails. Rated critical severity (CVSS 9
Camaleon CMS v2.7.0 was discovered to contain a Server-Side Template Injection (SSTI) vulnerability via the formats para
Authenticated remote code execution in Camaleon CMS 2.1.1 through 2.9.1 lets users who hold the custom_fields manage per
Camaleon CMS is a dynamic and advanced content management system based on Ruby on Rails. Rated high severity (CVSS 7.7),
Cross Site Scripting vulnerability in camaleon-cms v.2.7.5 allows remote attacker to execute arbitrary code via the cont
Camaleon CMS 0.1.7 to 2.6.0 doesn’t terminate the active session of the users, even after the admin changes the user’s p
Camaleon CMS releases before 2.9.3 let an authenticated user who holds only the 'media' permission escape the site's tem
Camaleon CMS releases before 2.9.2 enforce only authentication, not authorization, on the Admin::MediaController endpoin
In Camaleon CMS application, versions 0.0.1 to 2.6.0 are vulnerable to stored XSS, that allows an unauthenticated attack
In the 2.4 version of Camaleon CMS, Stored XSS has been discovered. Rated medium severity (CVSS 6.1), this vulnerability
Camaleon CMS versions 2.4.5.0 through 2.9.0, prior to commit f54a77e, contain a path traversal vulnerability in the AWS
Draft post creation in Camaleon CMS through 2.9.2 allows any authenticated low-privileged user to create and overwrite d
EUVD-2026-115239
GHSA-gxj9-c997-h74f
NVD
CVE.org
EPSS
Exploit-DB