SQL injection vulnerability in the backend module in the Developer Log (devlog) extension before 2.11.4 for TYPO3 allows remote editors to…

published 2015-06-16 11y ago modified 2026-06-17 4mo ago also EUVD-2015-4633

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

SQL injection vulnerability in the backend module in the Developer Log (devlog) extension before 2.11.4 for TYPO3 allows remote editors to execute arbitrary SQL commands via unspecified vectors.

Patch / fix

links 1

typo3.org/extensions/repository/view/devlog patch

Is CVE-2015-4613 in your stack? 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

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

CVSS scores

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

Classification

Weakness

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

References

typo3.org /extensions/repository/view/devlog
patch
typo3.org /teams/security/security-bulletins/typo3-extensions/typo3-ext-sa-2015-011/
vendor-advisory
securityfocus.com /bid/75257
vdb-entry

Sources

CVE List CVE-2015-4613
NVD CVE-2015-4613

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.