CVE-2025-30550
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 WPShop.ru CallPhone'r callphoner allows Stored XSS.This issue affects CallPhone'r: from n/a through <= 1.1.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 confidenceCSRF vulnerability in the CallPhone'r WordPress plugin allows attackers to craft malicious requests that result in Stored XSS. The lack of anti-CSRF protections enables authenticated users to be tricked into injecting malicious scripts that persist and execute for other users viewing the affected content.
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.
-
Identify if CallPhone'r plugin is installedCheck the WordPress plugin directory (wp-content/plugins/) for the CallPhone'r folder, or view the installed plugins list in WordPress admin under Plugins > Installed PluginsAffected if The CallPhone'r plugin folder exists in the plugins directory
-
Determine the installed plugin versionLocate the main plugin file (callphoner.php or similar) and read the version header (e.g., 'Version: 1.2.3') from the file header comments, or check the version displayed in the WordPress plugins admin pageAffected if The installed version matches or falls within any known affected version ranges for CVE-2025-30550
-
Inspect forms for nonce verificationExamine the plugin PHP files for form submissions and locate the form handlers. Search for calls to wp_verify_nonce, check_admin_referer, or wp_nonce_field functions within the code that processes form dataAffected if Form handlers lack nonce verification (no wp_verify_nonce, check_admin_referer, or similar anti-CSRF function calls)
-
Inspect AJAX handlers for nonce verificationSearch plugin PHP files for registered AJAX actions (add_action with wp_ajax_ or wp_ajax_nopriv_ prefixes) and examine whether each handler calls wp_verify_nonce or check_admin_referer before processing requestsAffected if AJAX handlers process requests without verifying nonces
-
Check for stored XSS vulnerabilitiesReview how user-supplied input from forms is stored and displayed. Examine both the input handling code (for sanitization functions like sanitize_text_field, esc_attr, etc.) and output rendering code (for output encoding like esc_html, esc_attr, wp_kses)Affected if User input is stored without proper sanitization and rendered without output encoding, allowing malicious script injection
Your environment is affected if the CallPhone'r plugin is installed and its forms or AJAX handlers lack proper nonce verification, enabling CSRF-to-Stored XSS attacks
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 WordPress nonces (anti-CSRF tokens) on all form submissions and AJAX handlers, combined with proper input sanitization and output encoding to prevent XSS execution.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30550 — 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-30550 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