CVE-2024-27191
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in inpersttion Slivery Extender slivery-extender allows Remote Code Inclusion.This issue affects Slivery Extender: from n/a through <= 1.0.2.
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 confidenceA code injection vulnerability in Slivery Extender versions up to 1.0.2 allows remote attackers to inject and execute arbitrary code through improper control of code generation. The vulnerability enables remote code inclusion, potentially giving attackers full control of the affected system.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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.
-
Confirm Slivery Extender installationLocate Slivery Extender files on the system - check common plugin/module directories for files named 'SliveryExtender', 'slivery', or similar. Use file system search commands (find, ls) to locate the software.Affected if Slivery Extender is present on the system and has not been patched to a version beyond 1.0.2
-
Identify installed versionExamine version metadata in the Slivery Extender files - check for version strings in configuration files, headers, composer.json, package.json, or the main extension file. Compare against the affected range (versions up to and including 1.0.2).Affected if The installed version is 1.0.2 or any earlier version
-
Check for eval usage with user inputSearch the Slivery Extender source code for eval() function calls. Review whether any eval statements accept or incorporate user-supplied data directly or indirectly through request parameters, form inputs, or API arguments.Affected if The code contains eval() statements that process user input without sanitization
-
Inspect dynamic include/require statementsSearch for include, require, include_once, or require_once statements in the Slivery Extender code that use variables (e.g., include($var), require $_GET['file']). Determine if these can be influenced by external user input.Affected if Dynamic include/require statements accept user-controllable input without validation
-
Review configuration for code execution featuresExamine Slivery Extender configuration files for settings that enable dynamic code execution, template injection, or plugin loading from user-specified paths. Look for options like 'allow_url_include', 'eval_enabled', or similar.Affected if Configuration enables or permits dynamic code generation from external sources
The environment is affected if Slivery Extender version 1.0.2 or earlier is installed AND dynamic code execution features (eval, include/require with user input) are enabled or accessible.
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 dataUpgrade to a patched version of Slivery Extender once available. Until then, implement strict input validation and disable any dynamic code execution features (eval, include/require with user input, etc.) that could enable code injection.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27191 — 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-2024-27191 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