CVE-2025-48320
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 cuckoohello 百度分享按钮 baidushare-wp allows Stored XSS.This issue affects 百度分享按钮: from n/a through <= 1.0.6.
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 Cross-Site Request Forgery (CSRF) vulnerability in the baidushare-wp WordPress plugin (versions <=1.0.6) allows authenticated administrators to be tricked into submitting crafted requests that result in Stored XSS. An attacker could inject malicious JavaScript into plugin settings that executes when other users view affected pages.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 baidushare-wp plugin is installedNavigate to WordPress admin dashboard > Plugins and look for 'baidushare-wp' in the installed plugins list, or inspect the wp-content/plugins/ directory for a baidushare-wp folderAffected if The plugin appears in the installed plugins list or directory
-
Identify the installed versionIn the WordPress plugins admin page, find the version number listed under the baidushare-wp plugin description, or check the plugin's main PHP file or readme.txt for the 'Version' headerAffected if The version number is 1.0.6 or lower
-
Verify admin settings forms lack CSRF protectionExamine the PHP files handling plugin settings (typically in the admin subdirectory or main plugin file). Search for occurrences of wp_nonce_field, wp_verify_nonce, nonce_field, or verify_nonce within form processing codeAffected if The settings forms that save plugin options do not contain WordPress nonce verification functions or tokens
-
Check if plugin settings are accessible to administratorsLog in as an administrator and access the baidushare-wp settings page in the WordPress admin dashboard (usually under Settings or a dedicated menu item)Affected if You can access and modify plugin settings as an authenticated administrator
-
Confirm stored XSS is possible in settingsWith admin access, inspect the plugin settings fields. If the saved values are output without sanitization in frontend pages, malicious JavaScript could be stored and executedAffected if Plugin settings values are saved and displayed on pages without proper output sanitization/escaping
A user is affected if the baidushare-wp plugin version is 1.0.6 or lower AND the plugin settings forms lack WordPress nonce verification, allowing attackers to trick administrators into storing malicious scripts.
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 a patched version of the plugin if available, or disable the plugin until a fix is released. Implementing anti-CSRF tokens (WordPress nonces) in all admin forms and validating nonce verification in form handlers will remediate the vulnerability.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48320 — 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-48320 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