dbcve.org
Liferay PortalApplication · Liferay

CVE-2011-1571

MEDIUM · 6.8 CVSS v2.0 Published 2011-05-07
Fix available
A fix is available. Upgrade to after 6.0.5 or later.
See remediation →
77/100
Remediation priority · High
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
Unspecified vulnerability in the XSL Content portlet in Liferay Portal Community Edition (CE) 5.x and 6.x before 6.0.6 GA, when Apache Tomcat is used, allows remote attackers to execute arbitrary commands 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 confidence

This is a command injection vulnerability in the XSL Content portlet of Lifer Portal CE 5.x and 6.x (before 6.0.6 GA) when running on Apache Tomcat. The vulnerability allows remote attackers to execute arbitrary commands on the underlying system through unspecified vectors related to XSL processing.

MitigationUpgrade Lifer Portal to version 6.0.6 GA or later. If immediate upgrade is not feasible, consider disabling or restricting access to the XSL Content portlet and/or deploying a WAF rule to filter malicious XSL requests.

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
Liferay PortalApplication
Affected:>= 5.1.0, <= 5.1.2>= 6.0.0, <= 6.0.5

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
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 checks

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

  1. Identify Lifer Portal version
    Locate the portal's version file or check the control panel 'Server > Information' section for the exact version number
    Affected if version is 5.1.0, 5.1.1, 5.1.2, 6.0.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, or 6.0.5
  2. Confirm Apache Tomcat is the application server
    Check the application server hosting the portal - look for Tomcat process, catalina.sh/catalina.bat, or check the server info via the portal's 'Server > Information' page
    Affected if the portal is running on Apache Tomcat
  3. Verify XSL Content portlet is deployed
    Navigate to the portal's control panel and check 'Plugin Installation > Portlets' for the XSL Content portlet, or check the deployed portlets directory for xslt-portlet or similar XSL-related portlet
    Affected if the XSL Content portlet is installed and available for use

You are affected if your Lifer Portal version is between 5.1.0 and 5.1.2 or between 6.0.0 and 6.0.5, running on Apache Tomcat, with the XSL Content portlet deployed.

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.

From vendor data
Upgrade available Upgrade to a release after 6.0.5
Interim mitigation

Upgrade Lifer Portal to version 6.0.6 GA or later. If immediate upgrade is not feasible, consider disabling or restricting access to the XSL Content portlet and/or deploying a WAF rule to filter malicious XSL requests.

Fix this in Liferay Portal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-1571 — 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-1571 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