CVE-2013-4871
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 · uneditedCross-site request forgery (CSRF) vulnerability in the TEQneers SEO Enhancements (tq_seo) extension before 5.0.1 for TYPO3 allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.
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 · moderate confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in the TEQneers SEO Enhancements (tq_seo) extension for TYPO3. The vulnerability allows remote attackers to potentially hijack the authentication of administrators or other authenticated users by tricking them into submitting malicious requests. CSRF attacks exploit the trust a website has in an authenticated user's browser, enabling attackers to perform unauthorized actions without directly stealing credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.0.0CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Verify if tq_seo extension is installedIn the TYPO3 backend, navigate to the Extension Manager or use the command line (typo3/cli_dispatch.phpsh ext) to list installed extensions. Look for 'tq_seo' or 'teqneers_seo_enhancements' in the list.Affected if The extension appears in the list of installed extensions.
-
Determine the installed version of tq_seoCheck the extension version by inspecting the file typo3conf/ext/tq_seo/ext_emconf.php (or typo3/ext/tq_seo/ext_emconf.php depending on TYPO3 version). Look for the 'version' field in the $EM_CONF array.Affected if The version number shown is 5.0.0 or lower (for example, 5.0.0, 4.5.0, 4.0.0, etc.).
-
Confirm the extension is active and has admin functionalityIn the TYPO3 backend Extension Manager, verify that the tq_seo extension is not only installed but also loaded and active. CSRF affects the extension when it is loaded and handling administrative actions.Affected if The extension status shows as 'Loaded' or 'Active' in the Extension Manager.
If the tq_seo extension is installed and active with version 5.0.0 or lower, the TYPO3 installation is vulnerable to CVE-2013-4871.
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 dataUpdate the tq_seo extension to version 5.0.1 or later which contains the CSRF fix. If immediate updating is not possible, consider disabling the extension until the patch can be applied.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4871 — 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-2013-4871 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