CVE-2026-4320
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 · uneditedAuthorization Bypass vulnerability in Creartia's ICMS software could allow an attacker to gain unauthorized access to protected features by manipulating the HTTP redirect headers of the login process, causing the script to continue running and enabling privilege escalation without the need for credentials.
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 · moderate confidenceAn authorization bypass vulnerability in Creartia's ICMS allows attackers to manipulate HTTP redirect headers during the login process, causing the application script to continue execution after a redirect should have occurred. This enables unauthorized access to protected administrative features and privilege escalation without valid credentials.
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
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/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 Creartia's ICMS installationCheck your web server's document root for CMS files and look for version indicators in meta tags, README files, or a version endpoint (e.g., /admin/about, /version). Use command: find /var/www -name '*.php' -path '*creartia*' 2>/dev/null or check your package manager if installed via package.Affected if Creartia's ICMS is present and the version cannot be confirmed as patched.
-
Inspect login redirect handlingLocate the login processing script (commonly login.php, auth.php, or similar in the admin or auth directories). Search for header('Location:') calls and examine whether the script continues execution (e.g., additional function calls, database queries) after issuing a redirect header without proper exit or die statements.Affected if The login script continues processing after sending a redirect header without validated session or authorization state.
-
Review HTTP redirect header validationExamine the codebase for functions that process or validate HTTP redirect headers (Location, Refresh, or custom redirect headers). Check if user-supplied input influences redirect destinations without sanitization or allowlist validation.Affected if Redirect headers accept arbitrary user-controlled values or lack server-side validation before being used.
-
Test administrative feature accessWith an unauthenticated or low-privilege session, attempt to access known admin endpoints (e.g., /admin/dashboard, /admin/users, /admin/settings). Observe if manipulating request headers (including redirect-related headers) allows access to protected pages without proper authentication.Affected if Administrative features are accessible without valid credentials or can be reached by manipulating redirect behavior.
-
Check session and authorization logicReview authentication and session management code to determine if authorization checks occur after any redirect logic. Verify that session validation is not conditional on redirect header presence or can be bypassed when redirects are intercepted or modified.Affected if Authorization verification depends on or can be circumvented by HTTP redirect header manipulation.
The environment is affected if Creartia's ICMS is running and the login redirect mechanism allows continued script execution or can be manipulated via HTTP redirect headers to bypass authorization checks for administrative features.
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 strict validation of all HTTP redirect headers and ensure authorization checks cannot be bypassed via header manipulation. Add mandatory session termination and proper access control verification before allowing any script execution after authentication events.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4320 — 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-4320 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