dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-42287

CRITICAL · 10.0 CVSS v4.0 Published 2026-05-08
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
Emlog is an open source website building system. Prior to version 2.6.11, direct SQL injection in article creation and update functions allows attackers to execute arbitrary SQL commands, potentially leading to complete database compromise, data theft, or system destruction. This issue has been patched in version 2.6.11.

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

Emlog prior to version 2.6.11 contains a direct SQL injection vulnerability in the article creation and update functions. Attackers can inject malicious SQL commands through unsanitized input fields when creating or updating articles, allowing arbitrary SQL execution on the underlying database. This can lead to complete database compromise, including unauthorized data access, modification, or deletion.

MitigationUpgrade Emlog to version 2.6.11 or later to patch the SQL injection vulnerability. If immediate patching is not possible, disable article creation/update functions until the patch can be applied.

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:H/SC:H/SI:H/SA:H/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 checks

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

  1. Confirm Emlog is installed
    Look for Emlog installation by checking for characteristic files (e.g., /admin/, index.php with emlog signature, or the presence of an 'include' directory with emlog core files)
    Affected if Emlog is present in the environment
  2. Identify the installed Emlog version
    Check the version file or constants file typically found in the Emlog installation root (often named 'version.php' or defined in 'init.php' or 'config.php'), or access the admin dashboard footer which often displays the version
    Affected if The discovered version is earlier than 2.6.11 (e.g., 2.6.10, 2.6.0, or any version below 2.6.11)
  3. Verify article creation and update functions are accessible
    Confirm that the article/create and article/update endpoints or admin functions are available and not explicitly disabled through configuration. Check if the user has permissions to access the article editor in the admin panel.
    Affected if The article creation and update functionality is enabled and accessible to users (authenticated or potentially unauthenticated depending on configuration)

You are affected if Emlog is installed with a version lower than 2.6.11 and the article creation/update functions are accessible in your environment.

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 Emlog to version 2.6.11 or later to patch the SQL injection vulnerability. If immediate patching is not possible, disable article creation/update functions until the patch can be applied.

Recommended fix High confidence

2.6.11

  1. 1. Backup your current Emlog installation and database before proceeding with any changes.
  2. 2. Download Emlog version 2.6.11 from the official source (github.com/emlog/emlog).
  3. 3. Replace the existing Emlog files with the new version 2.6.11 files, preserving your configuration and content files if needed.
  4. 4. Verify the upgrade was successful by logging into the admin panel.
  5. 5. Test the article creation and update functions to confirm the SQL injection vulnerability is remediated.
  6. 6. Review database logs for any suspicious activity that may indicate prior exploitation.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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