CVE-2026-8726
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 · uneditedThe extension fails to properly sanitize user input before using it in a database query. As a result, an unauthenticated attacker can inject arbitrary SQL through a URL parameter on pages using the "Date Menu of news articles" plugin. Exploitation requires the "Date Menu of news articles" plugin to be in use and the TypoScript/Plugin setting disableOverrideDemand not to be enabled.
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 · high confidenceThis is an unauthenticated SQL injection vulnerability in the TYPO3 'Date Menu of news articles' extension. The extension fails to sanitize user-supplied input from a URL parameter before incorporating it into a database query, allowing attackers to execute arbitrary SQL commands. Successful exploitation requires the vulnerable plugin to be in use with the disableOverrideDemand TypoScript/Plugin setting disabled.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the Date Menu of news articles extension is installedCheck the TYPO3 extension manager or composer.json for presence of the 'news' extension with a date menu component. Look for extension key 'news' or 'tx_news' in your installed extensions list.Affected if The extension is installed and the Date Menu plugin is in use on any page.
-
Check the extension versionRetrieve the installed version of the news extension from TYPO3's extension manager, composer.json, or by examining the ext_emconf.php file in the extension directory.Affected if The version matches or falls within any known affected version range for this CVE.
-
Verify the disableOverrideDemand TypoScript settingLocate the TypoScript setup for the news plugin (usually in the page TSconfig or the extension's TypoScript template). Search for the setting 'plugin.tx_news.settings.disableOverrideDemand' and check its value.Affected if The setting is either absent, set to 0, or set to false (meaning override is allowed and the vulnerability is present).
-
Identify if the Date Menu plugin is actively renderedCheck your TYPO3 page tree and content elements to see if any page is using the Date Menu plugin (usually a plugin content element of type 'News' with date menu display). Review the page's frontend output or database tt_content table for plugin usage.Affected if The Date Menu plugin is present on any live page and accessible without authentication.
Your environment is affected if the Date Menu of news articles extension is installed with a vulnerable version, the plugin is in use on a publicly accessible page, and the disableOverrideDemand setting is disabled or not set to 1.
Generated from the published advisory. Verify against your own configuration.
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 dataEnable the disableOverrideDemand setting in TypoScript as a temporary workaround, or ideally update to a patched version of the extension that properly sanitizes or parameterizes database queries.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-8726 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8726 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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