CVE-2026-49775
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 · uneditedUnauthenticated Broken Access Control in Welcart e-Commerce <= 2.11.28 versions.
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 confidenceThis is an unauthenticated broken access control vulnerability in the Welcart e-Commerce WordPress plugin versions 2.11.28 and prior. An attacker without any credentials can access functionality that should require authentication or proper authorization, potentially allowing unauthorized administrative or data access operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Welcart e-Commerce plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Welcart e-Commerce and read the version number from the plugin description. Alternatively, check the main plugin file (usceshop.class.php) in wp-content/plugins/usc-e-shop/ for the 'Version' header comment.Affected if Installed version is 2.11.28 or lower
-
Confirm plugin is activeVerify the Welcart e-Commerce plugin is currently activated in WordPress at Plugins > Installed Plugins. The vulnerability only applies when the plugin is active.Affected if Plugin is activated and version is 2.11.28 or lower
-
Identify exposed authentication-required functionsReview the plugin's AJAX handlers (typically in usceshop.class.php or separate action files) and admin page controllers. Look for functions that perform administrative or sensitive data operations without checking user authentication status.Affected if The plugin exposes endpoints that perform privileged operations without requiring authentication (WordPress nonce verification or current_user_can checks are missing)
-
Test unauthenticated endpoint accessSend a direct HTTP request to common Welcart AJAX endpoints (such as wp-admin/admin-ajax.php?action=usces_* or plugin-specific endpoints) without providing any authentication cookies or credentials. Observe whether the request is processed or returns data that should require login.Affected if Requests to protected plugin functions complete successfully without authentication tokens
You are affected if Welcart e-Commerce version 2.11.28 or prior is installed and active, and the plugin exposes admin or data functions that can be accessed without authentication.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Welcart e-Commerce to the latest version newer than 2.11.28. If immediate patching is not possible, restrict access to the affected plugin endpoints via web server configuration or disable the plugin until an update can be applied.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49775 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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