CVE-2025-30555
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 iiiryan WordPres 同步微博 wp2wb allows Stored XSS.This issue affects WordPres 同步微博: from n/a through <= 1.1.0.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the iiiryan WordPress 同步微博 (wp2wb) plugin allows attackers to craft malicious requests that result in Stored XSS. The plugin lacks proper CSRF protection mechanisms (such as nonces/tokens) on sensitive actions, enabling attackers to inject persistent malicious scripts into the plugin's data storage.
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.
-
Verify the wp2wb plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WordPress 同步微博 (wp2wb)' by iiiryan. Note the installed version number.Affected if The plugin is installed and active
-
Check the installed version against affected rangeCompare the installed version number to any available version information. Since no specific version range is provided, check if you are running an older or unmaintained version of the plugin.Affected if Running an outdated version of the plugin
-
Verify admin access to plugin settingsNavigate to the plugin's settings page (usually under Settings or the plugin's own menu) where social media synchronization settings can be configured.Affected if You have access to the plugin's configuration interface
-
Inspect plugin source for CSRF protectionExamine the plugin's PHP files (typically in wp-content/plugins/wp2wb/) for form submissions and AJAX actions. Look for the presence of wp_nonce_field(), check_admin_referer(), or nonce verification in the code handling state-changing operations.Affected if Forms and AJAX actions lack nonce verification (wp_nonce_field or check_admin_referer calls)
-
Check input handling for XSS vulnerabilitiesReview the plugin's code that processes and stores user input from forms, looking for proper sanitization functions (sanitize_text_field, esc_attr, etc.) and output escaping (esc_html, esc_js) when data is displayed.Affected if User input is stored without sanitization or output is not properly escaped
You are affected if the wp2wb plugin is installed, lacks nonce verification on sensitive actions, and does not properly sanitize/escape user input, allowing CSRF-triggered Stored XSS.
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 (nonces) on all state-changing forms and AJAX actions, and apply proper input sanitization and output escaping to prevent Stored XSS. Consider updating to a maintained plugin version or replacing with an alternative if unmaintained.
- 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-30555 — 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-30555 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