Camaleon CMS before 2.9.2 IDOR via Admin::CategoriesController
Only affects Camaleon CMS before 2.9.2 for users with category management permission on one Post Type, who could modify or delete categories of other Post Types. Fixed in 2.9.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.9.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. User has category management permission for one Post Type Category lookup is global rather than scoped to the authorized Post Type (vulnerable code)
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2.9.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Camaleon CMS, a content management system, is affected by this flaw in its category administration feature. An authenticated user with access to one post type can rename or delete categories belonging to other post types, which they should not be permitted to change.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
User has category management permission for one Post Type Category lookup is global rather than scoped to the authorized Post Type (vulnerable code)Upgrade to a fixed version: 2.9.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- owen2345 Camaleon CMS
fixed in 2.9.2
Evidence 5
- Patch
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120430
What does this mean?
The category lookup in the admin categories controller loads a category by ID without checking that it belongs to the Post Type the user is authorized for. A user with permission for one Post Type can therefore change or delete categories that belong to other Post Types by altering request parameters.Source: github.com, github.com
Am I affected, and how do I check?
Camaleon CMS versions before 2.9.2 are affected, and the issue requires a user with category management permission for at least one Post Type. To check, look at the installed Camaleon CMS version and confirm whether it is earlier than 2.9.2.Source: github.com, github.com
What should I do about it?
Upgrade Camaleon CMS to version 2.9.2 or later, which contains the fix. No workaround is listed in the facts, so upgrading is the stated remedy.Source: github.com, github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data