dbcve.org
Debian LinuxOperating system · Debian

CVE-2020-15227

CRITICAL · 9.8 CVSS v3.1 Published 2020-10-01
Fix available
A fix is available. Upgrade to 2.0.19 / 2.1.13 or later.
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
Nette versions before 2.0.19, 2.1.13, 2.2.10, 2.3.14, 2.4.16, 3.0.6 are vulnerable to an code injection attack by passing specially formed parameters to URL that may possibly leading to RCE. Nette is a PHP/Composer MVC Framework.

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 confidence

Nette PHP framework versions before 2.0.19, 2.1.13, 2.2.10, 2.3.14, 2.4.16, and 3.0.6 contain a code injection vulnerability where specially crafted URL parameters can be processed in an unsafe manner, potentially allowing remote code execution (RCE).

MitigationUpgrade Nette framework to version 2.0.19, 2.1.13, 2.2.10, 2.3.14, 2.4.16, or 3.0.6 or later via Composer to obtain the patched version.

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
Debian LinuxOperating system
Affected:= 9.0
ApplicationApplication
Affected:>= 2.0.0, < 2.0.19>= 2.1.0, < 2.1.13>= 2.2.0, < 2.2.10>= 2.3.0, < 2.3.14>= 2.4.0, < 2.4.16>= 3.0.0, < 3.0.6

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. Identify Nette Application installation
    Check for Nette presence in your PHP project by examining the composer.json file for 'nette/application' in the require section, or check the vendor/nette/application directory if present.
    Affected if Nette Application package is present in your project dependencies.
  2. Determine installed Nette Application version
    Run 'composer show nette/application' to display the installed version, or read the version from vendor/composer/installed.json under the nette/application entry.
    Affected if The version number is less than 2.0.19, 2.1.13, 2.2.10, 2.3.14, 2.4.16, or 3.0.6.
  3. Check for vulnerable routing configuration
    Examine your application bootstrap or router configuration file (typically app/RouterFactory.php, app/bootstrap.php, or config/routes.neon) for the use of Nette's Router with default or dynamic route factories.
    Affected if Your application uses Nette Router to process incoming URL parameters without custom sanitization.
  4. Verify Debian package version (if applicable)
    On Debian systems, run 'dpkg -l | grep nette' to list installed Nette packages, or 'apt-cache policy php-nette-application' to check available versions.
    Affected if The installed package version falls within the affected ranges listed in the CVE for Debian 9.0.

You are affected if Nette Application is installed and its version falls within the specified vulnerable ranges, and your application uses Nette Router to handle URL parameters.

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
Upgrade available Upgrade to 2.0.19 / 2.1.13 / 2.2.10 or later
Fixed in 2.0.192.1.132.2.10
Interim mitigation

Upgrade Nette framework to version 2.0.19, 2.1.13, 2.2.10, 2.3.14, 2.4.16, or 3.0.6 or later via Composer to obtain the patched version.

Recommended fix High confidence

Upgrade to Nette 2.0.19, 2.1.13, 2.2.10, 2.3.14, 2.4.16, or 3.0.6 (or later stable releases)

  1. 1. Identify the currently installed Nette framework version by checking your composer.json or vendor directory
  2. 2. Determine which version branch you are on (2.0.x, 2.1.x, 2.2.x, or 2.3.x)
  3. 3. Run 'composer require nette/nette:^2.0.19' (for 2.0.x branch), 'nette/nette:^2.1.13' (for 2.1.x), 'nette/nette:^2.2.10' (for 2.2.x), or 'nette/nette:^2.3.14' (for 2.3.x)
  4. 4. Alternatively, run 'composer update nette/nette' to get the latest version in your constraints
  5. 5. Test the application thoroughly in a staging environment to verify compatibility
  6. 6. Deploy the updated application to production
Caveat Review Nette changelog for breaking changes between your current version and target version; PHP version compatibility may also differ in newer releases

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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