dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-34461

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Zenario before 9.5.60437 uses Twig filters insecurely in the Twig Snippet plugin, and in the site-wide HEAD and BODY elements, enabling code execution by a designer or an administrator.

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 confidence

Zenario CMS before version 9.5.60437 allows code execution through insecure usage of Twig filters in the Twig Snippet plugin and in site-wide HEAD and BODY elements. An attacker with designer or administrator privileges can inject malicious Twig template code that executes arbitrary PHP code on the server.

MitigationUpgrade Zenario to version 9.5.60437 or later. Until patching is possible, disable the Twig Snippet plugin and restrict administrative access.

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed Zenario CMS version
    Access the admin panel and navigate to Admin > System > About Zenario, or check the version file in the installation directory (typically version.php or similar). Compare the version number to 9.5.60437.
    Affected if The installed version is earlier than 9.5.60437 (e.g., 9.5.60400, 9.4.x, etc.)
  2. Verify if the Twig Snippet plugin is enabled
    Log in as administrator and go to Admin > Plugins > Plugin Manager. Search for 'Twig Snippet' or navigate to the plugin configuration. Check whether the plugin is installed and enabled on any organ, slot, or document.
    Affected if The Twig Snippet plugin is installed and enabled on the site.
  3. Inspect site-wide HEAD and BODY element configurations
    In the admin panel, go to Configuration > Site Settings > HTML Head and Body Tags, or look for site-wide template configuration where custom HEAD and BODY content can be inserted. Examine any custom HTML or Twig code present in these fields.
    Affected if The site has custom Twig template code or dynamic content in the site-wide HEAD or BODY elements.
  4. Identify users with designer or administrator privileges
    Go to Admin > Users > Users and Groups. Review the user accounts and their assigned privileges. Look for any accounts with 'designer' or 'administrator' role levels.
    Affected if There are active user accounts with designer or administrator privileges, particularly any untrusted or compromised accounts.

You are affected if your Zenario CMS version is earlier than 9.5.60437 AND either the Twig Snippet plugin is enabled OR the site uses Twig syntax in HEAD/BODY elements, with at least one designer or administrator account present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Zenario to version 9.5.60437 or later. Until patching is possible, disable the Twig Snippet plugin and restrict administrative access.

Recommended fix Moderate confidence

Zenario 9.5.60437 or later

  1. 1. Check the current Zenario version installed on your system
  2. 2. Download Zenario version 9.5.60437 or later from the official source (zenar.io)
  3. 3. Back up your entire Zenario installation and database before upgrading
  4. 4. Install the upgraded version following the standard Zenario upgrade procedure
  5. 5. Verify the Twig Snippet plugin and site-wide HEAD/BODY elements are functioning correctly after upgrade
  6. 6. Confirm the upgrade was successful by checking the new version number
Caveat Review Zenario release notes for any breaking changes between your current version and 9.5.60437

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-34461 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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