CVE-2025-14357
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 Mega Store Woocommerce theme for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the setup_widgets() function in core/includes/importer/whizzie.php in all versions up to, and including, 5.9. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create arbitrary pages and modify site settings.
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 Mega Store Woocommerce theme for WordPress lacks a capability check on the setup_widgets() function in core/includes/importer/whizzie.php. This allows any authenticated user with Subscriber-level permissions or higher to call this function and create arbitrary pages or modify site settings, representing a Broken Access Control vulnerability.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Identify theme and versionNavigate to wp-content/themes/megastore and check the style.css file for the 'Version:' header. Alternatively, use WP CLI: wp theme list --status=active --format=tableAffected if The installed version is below 6.0 (the fixed version)
-
Locate vulnerable fileCheck if the file core/includes/importer/whizzie.php exists in the theme directory. Use: ls -la wp-content/themes/megastore/core/includes/importer/whizzie.phpAffected if The file exists and the theme version is below 6.0
-
Inspect setup_widgets function for capability checkOpen whizzie.php and search for the setup_widgets() function definition. Look for a current_user_can() call at the function start. Use grep: grep -n 'function setup_widgets' wp-content/themes/megastore/core/includes/importer/whizzie.phpAffected if The function exists but lacks a current_user_can() check before performing actions
-
Verify user roles existCheck if any user roles of Subscriber or higher exist in WordPress. Use WP CLI: wp user list --role=subscriber --format=count OR check via Users > All Users in wp-adminAffected if At least one user with Subscriber-level or higher access exists in the system
A user is affected if the Mega Store theme version is below 6.0, the whizzie.php file is present, the setup_widgets() function lacks a capability check, and any authenticated user with Subscriber-level or higher permissions exists on the site.
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 the theme to version 6.0 or later which includes the missing capability check. If no update is available, manually add a current_user_can() check to the setup_widgets() function before any data modification occurs.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14357 — 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-14357 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