CVE-2025-7821
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 WC Plus plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'pluswc_logo_favicon_logo_base' AJAX action in all versions up to, and including, 1.2.0. This makes it possible for unauthenticated attackers to update the site's favicon logo base.
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 WC Plus WordPress plugin versions up to 1.2.0 lack proper capability validation on the 'pluswc_logo_favicon_logo_base' AJAX action, allowing unauthenticated users to modify the site's favicon/logo base setting via the AJAX endpoint.
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.
-
Confirm WC Plus plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WC Plus', or check the plugin files in wp-content/plugins/wc-plus/ for the main PHP file and look for the Version header commentAffected if The plugin is installed and version is 1.2.0 or lower
-
Check installed plugin version numberRead the plugin header in wc-plus.php or the plugin's readme.txt file to find the exact version numberAffected if Version is 1.2.0 or any version prior to 1.2.1
-
Test unauthenticated AJAX accessSend a POST request to /wp-admin/admin-ajax.php with action=pluswc_logo_favicon_logo_base and a test logo_base parameter (e.g., nonce is not required for the vulnerable endpoint)Affected if The request returns a successful response (HTTP 200) without requiring authentication or a valid nonce
-
Inspect capability check in AJAX handlerLocate the PHP file registering the pluswc_logo_favicon_logo_base AJAX action (likely in includes/ or similar) and check if current_user_capability or check_ajax_referer is properly called before processing the requestAffected if No capability check or nonce verification is found before processing the logo_base update
A user is affected if WC Plus plugin version 1.2.0 or lower is installed AND the /wp-admin/admin-ajax.php endpoint responds to action=pluswc_logo_favicon_logo_base 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 the plugin to the latest version (1.2.1 or later) which includes proper capability checks. If no patch is available, disable the plugin or implement a web application firewall rule to block unauthenticated access to this AJAX action.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7821 — 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-7821 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