iceburgcrm/iceburgcrm authorization bypass in record save
Affects Iceburg CRM through 5.0.0 where roles are restricted through the permissions screen, not the stock seeding. No fixed version is listed.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Summary
Iceburg CRM through 5.0.0 lets a logged-in user with write access to one module write to modules they are not authorized to change, by prefixing request body keys with another module's ID. Remotely exploiting this flaw, an attacker can set their own role to Admin and gain access to administrative data.
Written by a model
Original description
Iceburg CRM through 5.0.0 contains an incorrect authorization vulnerability in Module::saveRecord() that allows authenticated users to write to unauthorized modules by prefixing request body keys with another module id. Attackers with write access to one module can submit crafted requests to POST /data/save or PUT /api/crm/{id} to set their role_id to Admin and access administrative data.
Who should check
Teams running iceburgcrm 5.0.0 or earlier with per-module role permissions, since saves via POST /data/save or PUT /api/crm/{id} can write to modules the role lacks.
“Affecting iceburgcrm <= 5.0.0”
What to do
Check whether your setup matches what the bug needs.
Attacker holds a user account whose role can write only one module Deployment restricts roles through the permissions screen (not the stock seeding, which grants every role every permission)Workaround: The checked facts give no workaround. Reviewing role permissions in the permissions screen is the only related step mentioned, but the facts do not say it removes the issue.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133874 (Iceburg CRM through 5.0.0 Authorization Bypass via Record Save), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133874 (entry last updated 2026-11-20):
Affected:
- Packagist package iceburgcrm/iceburgcrm: through 5.0.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Attacker holds a user account whose role can write only one module (source: https://github.com/iceburgcrm/iceburgcrm/issues/28)
- Deployment restricts roles through the permissions screen (not the stock seeding, which grants every role every permission) (source: https://github.com/iceburgcrm/iceburgcrm/issues/28)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-133874 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133874 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/iceburgcrm/iceburgcrm/issues/28
- https://github.com/iceburgcrm/iceburgcrm
- https://github.com/iceburgcrm/iceburgcrm/blob/v5.0.0/app/Models/Module.php#L283-L335
- https://github.com/iceburgcrm/iceburgcrm/blob/v5.0.0/app/Http/Controllers/Api/CRMController.php#L43-L54
- https://www.vulncheck.com/advisories/iceburg-crm-through-5.0.0-authorization-bypass-via-record-save
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133874
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133874"}.Affected versions
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Packagist packages
- Severity9.6/10CVSS 8.6, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 83 if added to CISA KEV
- Would score about 78 if CISA's SSVC rates exploitation active
- Would score about 40 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133874 |
| Record | NVD · CVE-2026-133874 |
| Other links 5 | |
| Report | GitHub · iceburgcrm/iceburgcrm · Issue #28 |
| Repository | GitHub · iceburgcrm/iceburgcrm · Repository |
| Repository | GitHub · iceburgcrm/iceburgcrm · app/Models/Module.php · L283-L335 |
| Repository | GitHub · iceburgcrm/iceburgcrm · app/Http/Controllers/Api/CRMController.php · L43-L54 |
| Link | vulncheck.com · advisories/iceburg-crm-through-5.0.0-authorization-bypass-via-record-save |
Questions about CVE-2026-133874
Is CVE-2026-133874 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
What does this mean?
A user whose role can write only one module can also write to other modules. An authenticated user can then set their own role_id to Admin and access administrative data.
Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-133874?
iceburgcrm/iceburgcrm (Packagist): through 5.0.0.
Source: cve.now feed data
Am I affected, and how do I check?
Versions through 5.0.0 are in scope, but the issue matters for deployments that restrict roles through the permissions screen, since the stock seeding grants every role every permission. Check how roles are configured in the permissions screen.
Source: github.com, vulncheck.com
How do I fix CVE-2026-133874?
The checked facts list no fixed version and no vendor patch ids, so no upgrade target can be given yet.
Source: github.com, vulncheck.com
What if there's no patch?
The checked facts give no workaround. Reviewing role permissions in the permissions screen is the only related step mentioned, but the facts do not say it removes the issue.
Source: github.com, vulncheck.com
Related
- CVE-2026-131287Remote Code Execution (RCE) through the REST API in Splunk SOAR
- CVE-2026-132659In Postgres Enterprise Manager (PEM), the row-level security policies on pem.job and pem.jobstep that apply to PEM agents do not limit an…
- CVE-2026-104099Fabio: Access-control bypass through unnormalized request paths
- CVE-2026-131271Improper Access Control through the REST API in Splunk SOAR
- CVE-2026-122247Budibase: Unauthenticated global-admin & database creation via tenant-confusion bypass of the one-time init guard (`POST…
- CVE-2026-131200Privilege Escalation through Threat Matching Searches in Splunk Enterprise Security
No corrections so far. Something wrong on this page? Report an error.