dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-48997

HIGH · 7.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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
e107 is a content management system (CMS). Versions 2.3.5 and earlier contain a command injection vulnerability in the ImageMagick resize destination path. In resize_image(), the source path is escaped with escapeshellarg(), but the destination path is inserted inside raw double quotes in the convert command; in the submit-news upload flow, that destination filename includes the first six characters of user-controlled news title input. Because the title filter removes literal spaces but not tab characters, and shell expansions such as $(...) and backticks can survive into the quoted destination argument, /bin/sh -c may evaluate attacker-controlled input. Exploitation is possible only when all of the following non-default settings are enabled: resize_method=ImageMagick, subnews_attach=1, upload_enabled=1, subnews_resize is numeric between 30 and 5000, and the attacker is a non-admin in classes permitted by both subnews_class and upload_class. This issue has been fixed in version 2.3.6.

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

e107 CMS versions 2.3.5 and earlier contain a command injection vulnerability in the ImageMagick resize function. The destination path in resize_image() is inserted into raw double quotes without escaping, while only the source path uses escapeshellarg(). In the submit-news upload flow, the destination filename incorporates the first six characters of user-controlled news title input. Since the title filter removes spaces but not tabs, shell expansions like $(...) and backticks survive and are evaluated by /bin/sh -c.

MitigationUpgrade to e107 version 2.3.6 which contains the patch. Alternatively, disable ImageMagick as the resize_method, or ensure the combination of non-default settings (subnews_attach=1, upload_enabled=1, numeric subnews_resize) required for exploitation are not all simultaneously enabled.

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
Unchanged
Confidentiality
Low
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/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. Identify e107 CMS version
    Locate the version file or check the admin dashboard for the installed e107 version. Common locations include e107_admin/system.php or a version constant in e107.php.
    Affected if Version is 2.3.5 or earlier
  2. Verify ImageMagick is configured as resize method
    Check the e107 configuration database or config file for the 'resize_method' setting. This is typically found in the e107_config table or e107.php configuration file.
    Affected if resize_method is set to ' imagemick' or 'ImageMagick' (case-insensitive)
  3. Confirm subnews_attach is enabled
    Check the e107 configuration for the 'subnews_attach' setting, typically in e107_config table or through the admin interface under news settings.
    Affected if subnews_attach is set to 1 or enabled
  4. Confirm upload functionality is enabled
    Check the e107 configuration for the 'upload_enabled' setting, typically in the file upload or news attachment settings in the admin panel.
    Affected if upload_enabled is set to 1 or enabled
  5. Verify subnews_resize has a numeric value
    Check the 'subnews_resize' configuration setting in e107_config or news settings. This should be set to a numeric value (pixel width) for the vulnerability to trigger.
    Affected if subnews_resize is set to a numeric value (greater than 0)

A user is affected if they are running e107 CMS version 2.3.5 or earlier with ImageMagick enabled as resize_method AND all three conditions (subnews_attach=1, upload_enabled=1, numeric subnews_resize) are simultaneously configured.

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 to e107 version 2.3.6 which contains the patch. Alternatively, disable ImageMagick as the resize_method, or ensure the combination of non-default settings (subnews_attach=1, upload_enabled=1, numeric subnews_resize) required for exploitation are not all simultaneously enabled.

Recommended fix High confidence

e107 version 2.3.6

  1. Back up the existing e107 installation and database before proceeding
  2. Download e107 version 2.3.6 from the official e107 repository or distribution source
  3. Replace the existing e107 files with the version 2.3.6 files, preserving any custom configurations if necessary
  4. If using ImageMagick resize_method, verify the configuration settings after upgrade
  5. Test the upgrade in a staging environment before deploying to production

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48997 — 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-2026-48997 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