dbcve.org
Welcart E CommerceWordPress extension · Welcart

CVE-2016-4825

MEDIUM · 5.6 CVSS v3.1 Published 2016-06-25
Fix available
A fix is available. Upgrade to 1.8.3 or later.
See remediation →
65/100
Remediation priority · Elevated
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 Collne Welcart e-Commerce plugin before 1.8.3 for WordPress allows remote attackers to conduct PHP object injection attacks and execute arbitrary PHP code via crafted serialized data.

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

The Collne Welcart e-Commerce plugin before version 1.8.3 for WordPress contains a PHP object injection vulnerability. Attackers can exploit unsafe deserialization of user-supplied data by injecting crafted serialized PHP objects, potentially leading to arbitrary code execution on the affected server.

MitigationUpgrade the Collne Welcart e-Commerce plugin to version 1.8.3 or later, which contains the fix for this vulnerability.

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 E CommerceWordPress extension
Affected:< 1.8.3

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

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

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. Verify WordPress installation exists
    Check for the presence of WordPress core files (wp-config.php, wp-includes directory) in the web root directory.
    Affected if WordPress is not installed, the plugin cannot be present.
  2. Check if Welcart e-Commerce plugin is installed
    Look for the plugin directory at wp-content/plugins/usc-e-shop/ or check via WordPress admin dashboard under Plugins > Installed Plugins.
    Affected if The plugin is not installed, this CVE does not apply.
  3. Determine installed plugin version
    Open the main plugin file (usc-e-shop/usc-e-shop.php) and locate the 'Version' header comment, or check the plugin details in WordPress admin dashboard.
    Affected if The installed version is less than 1.8.3 (e.g., 1.8.2, 1.8.1, 1.7.x, etc.).
  4. Confirm plugin is active
    Verify the plugin status in WordPress admin dashboard under Plugins > Installed Plugins, or check the active_plugins option in wp_options database table.
    Affected if The plugin is active and processing requests, the unsafe deserialization vulnerability is reachable.

You are affected if Welcart e-Commerce plugin is installed and active with a version number lower than 1.8.3.

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 1.8.3 or later
Fixed in 1.8.3
Interim mitigation

Upgrade the Collne Welcart e-Commerce plugin to version 1.8.3 or later, which contains the fix for this vulnerability.

Fix this in Welcart E Commerce Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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