CVE-2025-4200
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 Zagg - Electronics & Accessories WooCommerce WordPress Theme theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.4.1 via the load_view() function that is called via at least three AJAX actions: 'load_more_post', 'load_shop', and 'load_more_product. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
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 Zagg - Electronics & Accessories WooCommerce WordPress theme is vulnerable to Local File Inclusion via the load_view() function, which is exposed through three unauthenticated AJAX actions ('load_more_post', 'load_shop', 'load_more_product'). Attackers can include and execute arbitrary files on the server, enabling PHP code execution and bypass of access controls.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify Zagg theme installationCheck for the theme directory at wp-content/themes/zagg or wp-content/themes/zagg-electronics-accessories-woocommerce in the WordPress file systemAffected if The theme directory exists in the WordPress themes folder
-
Determine installed theme versionRead the Version: field from the style.css file header within the theme directoryAffected if The version cannot be determined, is older than any patched version, or falls within an affected version range
-
Confirm vulnerable AJAX actions are registeredSearch the theme's functions.php file for add_action calls containing 'load_more_post', 'load_shop', or 'load_more_product' hooksAffected if Any of these three AJAX action hooks are registered, particularly if hooked to wp_ajax_nopriv_ or wp_ajax_ for unauthenticated access
-
Locate the load_view() functionSearch the theme source code for the load_view() function definition and verify it accepts a parameter used in file inclusion operations (such as include, include_once, require, or require_once)Affected if The load_view() function exists and uses user-supplied input in file inclusion operations without proper sanitization
-
Test AJAX endpoint accessibilitySend a request to /wp-admin/admin-ajax.php with action=load_more_post (or load_shop, load_more_product) without authenticationAffected if The endpoint responds without requiring authentication, indicating the vulnerable function is exposed
The environment is affected if the Zagg theme is installed and the load_view() function with its vulnerable AJAX actions is accessible to unauthenticated users.
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.
dbcve · scopedUpdate the theme to a patched version if available; if no update exists, remove or disable the theme, or implement WAF rules/WordPress hook modifications to block access to the vulnerable AJAX endpoints.
- The Zagg theme is a discontinued commercial ThemeForest product with no publicly available patched version.
- Replace the vulnerable Zagg theme with a currently maintained theme from WordPress.org repository or a supported theme vendor.
- If replacement is not immediately possible, disable the AJAX actions 'load_more_post', 'load_shop', and 'load_more_product' by adding the following to your theme's functions.php: remove_action('wp_ajax_load_more_post', 'load_view'); remove_action('wp_ajax_nopriv_load_more_post', 'load_view'); remove_action('wp_ajax_load_shop', 'load_view'); remove_action('wp_ajax_nopriv_load_shop', 'load_view'); r
- Alternatively, disable the theme entirely and use a default WordPress theme until replacement is complete.
- Audit the server for any already uploaded malicious files in the wp-content/uploads directory and other writable locations.
- Reset all user passwords and regenerate API keys as a precaution since remote code execution was possible.
Generated from the published advisory — verify against the referenced sources before acting.
- 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-4200 — 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-4200 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