Security readout for executives and security teams
Plain-English summary
This CVE affects legacy Zend Framework 2.3.x applications before 2.3.6. A flaw in the CSRF validator could let invalid token identifiers bypass intended request-forgery protections, depending on application use. The source bundle does not provide CVSS, CWE, or active exploitation evidence.
Executive priority
Treat this as a legacy application hygiene issue unless Zend Framework 2.3.x is present in exposed business-critical systems. Prioritize confirmation and upgrade planning over emergency response.
Technical view
CVE-2015-1786 is a CSRF issue in Zend/Validator/Csrf in Zend Framework 2.3.x before 2.3.6 involving null or malformed token identifiers. The provided data identifies the fixed boundary as 2.3.6 but does not include detailed affected CPEs or scoring.
Likely exposure
Exposure is most likely in older PHP applications using Zend Framework 2.3.x before 2.3.6 and relying on Zend/Validator/Csrf for form or state-changing request protection.
Exploitation context
The bundle does not cite known exploitation and KEV is false. Risk depends on whether an exposed application uses the vulnerable CSRF validator around sensitive state-changing actions.
Researcher notes
Public metadata in the bundle is sparse: no CVSS, CWE, or structured CPEs are provided. The strongest facts are the component, vulnerable version range, malformed or null token identifier condition, and fixed version boundary.
Mitigation direction
- Upgrade Zend Framework 2.3.x deployments to 2.3.6 or later where applicable.
- Check vendor changelog and distribution advisories for backported fixes.
- Prioritize internet-facing applications with authenticated state-changing workflows.
- Retire or isolate unsupported legacy Zend Framework applications.
Validation and detection
- Inventory applications and dependency manifests for Zend Framework 2.3.x versions.
- Confirm whether Zend/Validator/Csrf is used for request protection.
- Verify deployed versions are 2.3.6 or include a vendor backport.
- Add regression tests for null and malformed CSRF token identifiers.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2015-1786 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://framework.zend.com/changelog/2.3.6CVE reference · x_refsource_CONFIRM
- https://bugzilla.redhat.com/show_bug.cgi?id=1207781CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.