dbcve.org
Wec Discussion ForumTYPO3 extension · Guidestar

CVE-2011-3584

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-26
Fix available
A fix is available. Upgrade to 2.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The TYPO3 Core wec_discussion extension before 2.1.1 is vulnerable to SQL Injection due to improper sanitation of user-supplied input.

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 confidence

SQL injection vulnerability in the TYPO3 wec_discussion extension versions prior to 2.1.1, caused by improper sanitization of user-supplied input. Attackers can inject malicious SQL queries through input fields to manipulate database operations.

MitigationUpgrade the wec_discussion extension to version 2.1.1 or later to obtain the patch. If immediate upgrade is not feasible, disable the extension to prevent exploitation.

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
Wec Discussion ForumTYPO3 extension
Affected:< 2.1.1

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if wec_discussion extension is installed
    Access the TYPO3 Extension Manager or check the extension directory (typo3conf/ext/) for the wec_discussion folder. Alternatively, query the TYPO3 extension database table (usually tx_extensionmanager_extensions) for the wec_discussion extension.
    Affected if The extension folder exists in the TYPO3 installation or appears in the extension database.
  2. Retrieve the installed version number
    Open the ext_emconf.php file located in the wec_discussion extension directory. Look for the 'version' field in the EM_CONF array. Alternatively, view the extension details in the TYPO3 Extension Manager interface.
    Affected if Unable to determine version or extension is not present.
  3. Compare version against the vulnerable threshold
    Review the version number found in the ext_emconf.php file. The vulnerable range is any version prior to 2.1.1 (for example: 2.1.0, 2.0.x, 1.x.x).
    Affected if The installed version is below 2.1.1 (for example: 2.1.0, 2.0.1, 2.0.0, 1.5.2).
  4. Verify the extension is actively enabled
    Check the TYPO3 backend under Admin Tools > Extension Manager > Extensions. Confirm that wec_discussion shows as 'Loaded' or 'Installed' and is not disabled. Alternatively, check the localconf.php or PackageStates.php for extension status.
    Affected if The extension is loaded/enabled in the TYPO3 configuration.

The environment is affected if the wec_discussion extension is installed, loaded, and running a version lower than 2.1.1.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2.1.1 or later
Fixed in 2.1.1
Interim mitigation

Upgrade the wec_discussion extension to version 2.1.1 or later to obtain the patch. If immediate upgrade is not feasible, disable the extension to prevent exploitation.

Recommended fix Moderate confidence

we c_discussion extension version 2.1.1

  1. Backup your TYPO3 database and all files before making any changes
  2. Access the TYPO3 Extension Manager in the backend
  3. Locate the 'wec_discussion' extension in the installed extensions list
  4. Update the extension to version 2.1.1 or later
  5. Clear all TYPO3 caches (via Install Tool or command line)
  6. Verify the extension is functioning correctly by testing discussion forum features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wec Discussion Forum Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-3584 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-3584 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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