CVE-2025-46492
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 Pham Thanh Call Now PHT Blog call-now-coccoc-pht-blog allows Stored XSS.This issue affects Call Now PHT Blog: from n/a through <= 2.4.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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the Call Now PHT Blog WordPress plugin (versions <= 2.4.1) allows attackers to trick authenticated administrators into inadvertently submitting malicious requests that store XSS payloads in the plugin's settings or display elements.
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.
-
Check if Call Now PHT Blog plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Call Now PHT Blog'. Alternatively, check the /wp-content/plugins/ directory for the plugin folder.Affected if The plugin is installed and active
-
Verify the installed version is vulnerableIn the WordPress Plugins page, find Call Now PHT Blog and note the version number displayed. Compare your version against the affected range (versions <= 2.4.1).Affected if Version is 2.4.1 or lower
-
Inspect plugin admin actions for missing CSRF protectionAccess the plugin PHP files via FTP or file manager in /wp-content/plugins/. Search for admin action handlers that process form submissions or AJAX requests. Look for the presence of wp_verify_nonce() or check_admin_referer() functions and nonce fields in any admin forms.Affected if Admin actions lack nonce verification and forms do not include nonce fields
-
Check for proper data sanitization and escapingIn the plugin PHP files, locate where user-supplied data is saved to settings and where it is output for display. Verify that input uses sanitization functions (such as sanitize_text_field) and output uses escaping functions (such as esc_html or esc_attr).Affected if User input is saved without sanitization or displayed without escaping
A user is affected if the Call Now PHT Blog plugin version is 2.4.1 or lower and admin actions are missing CSRF token verification or fail to sanitize/escape user-supplied data.
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 the latest plugin version. Until then, enforce CSRF protection (nonces) on all admin actions and ensure all user-supplied data is properly sanitized before storage and escaped on output.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46492 — 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-46492 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