CVE-2025-32576
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Agence web Eoxia - Montpellier WP shop wpshop allows Upload a Web Shell to a Web Server.This issue affects WP shop: from n/a through <= 2.6.1.
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 confidenceA CSRF vulnerability in WP shop plugin versions <=2.6.1 allows authenticated administrators to be tricked into unknowingly uploading malicious files (web shells) via forged HTTP requests. The attacker exploits the lack of anti-CSRF tokens on the file upload functionality to execute arbitrary code on the server.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Check WP shop plugin versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate the 'WP shop' (or 'WP Shop' or similar) plugin and read the version number displayed. Compare it against the affected range: versions <=2.6.1 are vulnerable.Affected if Installed version is 2.6.1 or lower.
-
Verify file upload functionality existsAccess the WordPress admin area and look for file upload forms in the plugin settings pages. Typical paths include /wp-admin/admin.php?page=wp_shop_settings or similar upload-enabled pages within the plugin menu.Affected if The plugin includes any file upload feature in its admin interface.
-
Inspect upload endpoint for anti-CSRF tokensView the HTML source of the file upload page (right-click > View Page Source). Search for the form element handling the upload and check if it contains a hidden input with a nonce value such as 'wp_nonce', '_wpnonce', or a token field. Also check the form action URL for nonce verification in the request parameters.Affected if The upload form lacks any nonce token field and the request does not include CSRF protection parameters.
-
Confirm administrator access to upload featureLog in as an administrator and navigate to the file upload section of the plugin. Attempt to access the upload functionality to verify that authenticated admin users can trigger the vulnerable endpoint.Affected if Administrator users can access and submit files to the upload endpoint without additional CSRF validation.
Your environment is affected if the WP shop plugin version is 2.6.1 or lower AND the file upload functionality is present and missing anti-CSRF token protection on the upload form or request.
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 dataImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations, particularly the file upload endpoint, and add server-side validation to restrict uploaded files to expected types only.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32576 — 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-32576 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