dbcve.org
Debian LinuxOperating system · Debian

CVE-2014-4913

MEDIUM · 6.1 CVSS v3.1 Published 2019-12-15
Fix available
A fix is available. Upgrade to 2.2.7 / 2.3.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
ZF2014-03 has a potential cross site scripting vector in multiple view helpers

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

Cross-site scripting (XSS) vulnerability in multiple Zend Framework view helpers allows attackers to inject malicious scripts through unsanitized user input rendered in web pages.

MitigationUpdate Zend Framework to the latest version containing the fix, or apply output encoding/sanitization in affected view helpers to neutralize XSS vectors.

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:= 8.0
Zend FrameworkApplication
Affected:< 2.2.7>= 2.3.0, < 2.3.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 installed Zend Framework version
    Check your project's composer.json, vendor/Zend/Version.php, or run 'composer show zendframework/zend-framework' to determine the exact version number
    Affected if version is < 2.2.7 OR (>= 2.3.0 AND < 2.3.1)
  2. Confirm Debian Linux version if applicable
    Run 'cat /etc/debian_version' or 'lsb_release -a' to check if the system is Debian 8.0
    Affected if running Debian 8.0 with bundled vulnerable Zend Framework
  3. Identify use of Zend view helpers in application
    Search codebase for usage of Zend view helpers, particularly those that render user input (search for 'Zend_View_Helper' or '$this->view' in PHP files)
    Affected if application uses Zend view helpers to render data
  4. Check for unsanitized user input in view scripts
    Review .phtml view template files for instances where request parameters ($_GET, $_POST) or user-supplied data is output without escaping (e.g., missing $this->escape() or htmlspecialchars())
    Affected if view templates render user input without output encoding

You are affected if your Zend Framework version falls within < 2.2.7 or >= 2.3.0 to < 2.3.1 (or Debian 8.0 with bundled vulnerable version) AND your application uses view helpers that render unsanitized user input in web pages.

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.

From vendor data
Upgrade available Upgrade to 2.2.7 / 2.3.1 or later
Fixed in 2.2.72.3.1
Interim mitigation

Update Zend Framework to the latest version containing the fix, or apply output encoding/sanitization in affected view helpers to neutralize XSS vectors.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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