dbcve.org
Xt CommerceApplication

CVE-2011-5011

MEDIUM · 6.8 CVSS v2.0 Published 2011-12-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Multiple cross-site request forgery (CSRF) vulnerabilities in xt:Commerce 3.0.4 SP2.1 and possibly earlier allow remote attackers to hijack the authentication of Admins for requests that (1) set a New user to Admin via the cID parameter to a statusconfirm action in admin/customers.php and (2) grant permissions to users via the cID parameter to a save action in admin/accounting.php.

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

CSRF vulnerability in xt:Commerce 3.0.4 SP2.1 allows remote attackers to hijack admin sessions. The admin/customers.php statusconfirm action lacks anti-CSRF protection on the cID parameter, enabling privilege escalation to admin. Similarly, admin/accounting.php save action on cID permits unauthorized permission grants. An attacker can trick logged-in admins into visiting malicious pages that silently execute these privileged actions.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing admin actions, specifically the statusconfirm and save endpoints. Add SameSite cookie attributes and require re-authentication for sensitive privilege modifications.

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
Xt CommerceApplication
Affected:= 3.0.4

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 the installed xt:Commerce version
    Locate the version file or admin panel 'About' section that displays the software version. Common locations include a version.php file in the root directory or the admin dashboard footer.
    Affected if The installed version is exactly 3.0.4 (or falls within the 3.0.4.x family)
  2. Verify admin/customers.php exists
    Access the file admin/customers.php in the web root. Check for the presence of a 'statusconfirm' action handling code that processes the cID parameter.
    Affected if The file exists and contains a statusconfirm action that accepts a cID parameter without anti-CSRF validation
  3. Verify admin/accounting.php exists
    Access the file admin/accounting.php in the web root. Check for the presence of a 'save' action handling code that processes the cID parameter.
    Affected if The file exists and contains a save action that accepts a cID parameter without anti-CSRF validation
  4. Inspect for CSRF token validation
    Review the source code of both admin/customers.php (statusconfirm) and admin/accounting.php (save) endpoints. Search for token validation logic such as 'token', 'csrf', or 'confirm' token checks before processing the cID parameter.
    Affected if No CSRF token or anti-CSRF validation routine is found in the code handling these actions
  5. Confirm admin session accessibility
    Verify that the admin interface is exposed and reachable. Check whether the admin panel requires authentication or is protected by any access controls.
    Affected if The admin panel is accessible and the vulnerable endpoints can be triggered by a logged-in administrator

You are affected if running xt:Commerce 3.0.4 and the admin/customers.php and admin/accounting.php endpoints lack anti-CSRF token validation on their statusconfirm and save actions respectively.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing admin actions, specifically the statusconfirm and save endpoints. Add SameSite cookie attributes and require re-authentication for sensitive privilege modifications.

Fix this in Xt Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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