CVE-2023-26546
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 · uneditedEuropean Chemicals Agency IUCLID before 6.27.6 allows remote authenticated users to execute arbitrary code via Server Side Template Injection (SSTI) with a crafted template file. The attacker must have template manager permission.
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 confidenceIUCLID before 6.27.6 is vulnerable to Server Side Template Injection (SSTI) allowing authenticated users with template manager permissions to execute arbitrary code by uploading crafted malicious template files. This occurs due to unsafe template rendering in the application's template management functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.15.0, < 6.27.6CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed IUCLID versionCheck the application version displayed in the IUCLID interface (typically in the About or Help section) or check the deployment/configuration files for the version numberAffected if The installed version is >= 5.15.0 and < 6.27.6
-
Verify template manager role existsCheck user roles and permissions in the IUCLID admin console or user management section for a 'Template Manager' or equivalent roleAffected if A Template Manager role is present and assigned to any user
-
Check if template management is accessibleNavigate to the template management functionality in IUCLID (typically under Administration or Tools menu) and verify the feature is availableAffected if Template management functionality is accessible to users with the template manager role
-
Review recent template uploadsInspect the template upload history or template storage directory for any recently added or modified template files, particularly files with unusual extensions or unexpected contentAffected if There are recently uploaded templates that were not created by trusted administrators or appear suspicious
A user is affected if they are running IUCLID version 5.15.0 through 6.27.5 AND have the template manager role enabled, allowing potential SSTI exploitation through the template upload feature.
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.
dbcve · scoped6.27.6
Upgrade IUCLID to version 6.27.6 or later. Until then, restrict template manager permissions to only trusted administrators and monitor for suspicious template uploads.
6.27.6
- 1. Identify current IUCLID version by checking the application's 'About' section or system information
- 2. If running version 5.15.0 or higher but below 6.27.6, plan for upgrade to version 6.27.6 or later
- 3. Back up the existing IUCLID database and configuration files before proceeding
- 4. Download IUCLID version 6.27.6 or later from the official ECHA IUCLID distribution channel
- 5. Stop the IUCLID application service
- 6. Install the new version following the official installation/upgrade documentation
- 7. Start the IUCLID application service
- 8. Verify the upgrade was successful by checking the version number in the 'About' section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26546 — 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-2023-26546 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