CVE-2025-12979
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 · uneditedThe Welcart e-Commerce plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'usces_export' action in all versions up to, and including, 2.11.24. This makes it possible for unauthenticated attackers to access configured payment credentials (ex. PayPal api secret) , as well as business contact details, mail templates, and other operational settings tied to the store.
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 confidenceThe Welcart e-Commerce WordPress plugin lacks a capability check on the 'usces_export' AJAX action, allowing unauthenticated attackers to trigger the export function. This exposes sensitive data including payment gateway credentials (e.g., PayPal API secrets), business contact information, mail templates, and store operational settings.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
-
Confirm Welcart e-Commerce plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Welcart e-Commerce' or check the plugin files in wp-content/plugins/usc-e-shop/ for the main PHP file and its version headerAffected if The plugin is not present in the WordPress installation
-
Identify installed plugin versionOpen the main plugin file (e.g., usc-e-shop.php) and locate the 'Version:' comment in the file header, or view the plugin details in WordPress admin Plugins pageAffected if Version is below 2.11.25 (the fixed version)
-
Verify AJAX endpoint existsCheck if the 'usces_export' AJAX action is registered by searching for 'add_action(\'wp_ajax_usces_export\'' or 'wp_ajax_nopriv_usces_export' in the plugin PHP files, or attempt a request to /wp-admin/admin-ajax.php?action=usces_export (note: this is for verification only, not exploitation)Affected if The usces_export action is registered without proper capability checks
-
Confirm lack of capability checkReview the plugin code handling the usces_export AJAX action and verify if current_user_can() or a similar capability check is performed before executing the export functionAffected if No capability check exists before processing the export request
-
Check for nonce verificationExamine the AJAX handler code to determine if a nonce verification (wp_verify_nonce or check_ajax_referer) is performed on the usces_export actionAffected if No nonce verification is implemented alongside the export handler
The environment is affected if Welcart e-Commerce plugin version is below 2.11.25 and the usces_export AJAX action is accessible without authentication or capability validation.
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 to version 2.11.25 or later which includes the capability fix. If no update is available, add a capability check (e.g., current_user_can('manage_options')) and nonce verification to the usces_export AJAX handler.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12979 — 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-2025-12979 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