yag and pt_extbase extensions for TYPO3 allow remote attackers to bypass access restrictions

published 2014-10-03 12y ago modified 2026-06-17 4mo ago also GHSA-46fq-683f-2jwq , EUVD-2014-6174

cvss: 7.5; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits: 0; none known

The Ajax dispatcher for Extbase in the Yet Another Gallery (yag) extension before 3.0.1 and Tools for Extbase development (pt_extbase) extension before 1.5.1 allows remote attackers to bypass access restrictions and execute arbitrary controller actions via unspecified vectors.

Patch / fix

fixed in 2 links 2

packagist dl/yag 3.0.1
packagist punktde/pt_extbase 1.5.1

github.com/YAG-Gallery/yag@4ab6ca1 commit
github.com/punktDe/pt_extbase@9969635 commit

Is CVE-2014-6289 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages

ecosystem	package	affected	fixed in
packagist	dl/yag	<3.0.1	3.0.1
packagist	punktde/pt_extbase	<1.5.1	1.5.1

Classification

Weakness

CWE-264 Permissions, Privileges, and Access Controls
CWE-284 Improper Access Control

References

Sources

CVE List CVE-2014-6289
GitHub Advisory GHSA-46fq-683f-2jwq
NVD CVE-2014-6289

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.