dbcve.org
Welcart PluginPlugin / extension · Welcart

CVE-2012-5178

MEDIUM · 6.8 CVSS v2.0 Published 2012-12-19
Fix available
A fix is available. Upgrade to after 1.2.1 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
Cross-site request forgery (CSRF) vulnerability in the Welcart plugin before 1.2.2 for WordPress allows remote attackers to hijack the authentication of arbitrary users for requests that complete a purchase.

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

CSRF vulnerability in the Welcart WordPress e-commerce plugin before version 1.2.2 allows remote attackers to trick authenticated users into completing unauthorized purchase transactions by forging requests that hijack the user's session.

MitigationUpdate Welcart plugin to version 1.2.2 or later, which should include proper anti-CSRF token (nonce) validation on purchase forms and action endpoints.

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
Welcart PluginPlugin / extension
Affected:<= 1.2.1= 0.5= 0.9.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
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. Locate Welcart plugin version
    Navigate to WordPress admin dashboard > Plugins > Welcart e-Commerce and view the installed version number displayed under the plugin name
    Affected if version number is 1.2.1 or lower, or specifically 0.5 or 0.9.1
  2. Identify plugin file path
    Check the plugin header in wp-content/plugins/usc-e-shop/functions/version.php or the main plugin file for the defined version constant
    Affected if the version constant WELCART_VERSION or similar indicates an affected version
  3. Verify purchase functionality is active
    Navigate to the frontend of the WordPress site and determine if the Welcart shopping cart, product pages, or checkout flow is accessible and in use
    Affected if any Welcart purchase or cart functionality is publicly accessible or available to logged-in users
  4. Confirm admin access exists
    Verify you have administrator-level access to the WordPress installation to inspect plugin configurations
    Affected if you can access the WordPress admin panel and plugin settings (required to verify the version)

Your environment is affected if the installed Welcart plugin version is 1.2.1 or lower, or specifically 0.5 or 0.9.1, and the purchase/transaction features are accessible to users.

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 1.2.1
Interim mitigation

Update Welcart plugin to version 1.2.2 or later, which should include proper anti-CSRF token (nonce) validation on purchase forms and action endpoints.

Fix this in Welcart Plugin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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