Skip to content
Fencer Intel
critical 9.8

CVE-2016-6233 json

Zend Framework Allows SQL Injection

published 2017-02-16 9 y ago modified 2026-06-17 4 mo ago also GHSA-p9hp-3gpv-52w3 , EUVD-2022-4721

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

The (1) order and (2) group methods in Zend_Db_Select in the Zend Framework before 1.12.19 might allow remote attackers to conduct SQL injection attacks via vectors related to use of the character pattern [\w]* in a regular expression.

Patch / fix

  • packagist zendframework/zendframework 1.12.19
  • packagist zendframework/zendframework1 1.12.19

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-6233 updated cvss 5.4

ZendFramework: Potential SQL injection in ORDER and GROUP statements of Zend_Db_Select

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.05% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • framework.zend.com https://framework.zend.com/security/advisory/ZF2016-02 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist zendframework/zendframework
<1.12.19
1.12.19
packagist zendframework/zendframework1
<1.12.19
1.12.19

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.