CVE-2025-46492
📋 TL;DR
A Cross-Site Request Forgery (CSRF) vulnerability in the Call Now PHT Blog WordPress plugin allows attackers to inject malicious scripts via stored XSS. When exploited, this can lead to session hijacking, data theft, or website defacement. WordPress administrators using vulnerable plugin versions are affected.
💻 Affected Systems
- Call Now PHT Blog WordPress Plugin
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Attackers could hijack administrator sessions, steal sensitive data, deface websites, or install backdoors for persistent access.
Likely Case
Attackers inject malicious scripts to steal session cookies or redirect users to phishing sites, compromising user accounts.
If Mitigated
With proper CSRF tokens and input validation, the attack vector is blocked, preventing XSS payload execution.
🎯 Exploit Status
Exploitation requires tricking an authenticated administrator into clicking a malicious link; CSRF to XSS chain is well-documented.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 2.4.2 or later
Restart Required: No
Instructions:
1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'Call Now PHT Blog' and click 'Update Now'. 4. Verify the plugin version is 2.4.2 or higher.
🔧 Temporary Workarounds
Disable Plugin
allTemporarily deactivate the vulnerable plugin to prevent exploitation.
wp plugin deactivate call-now-coccoc-pht-blog
Implement CSRF Protection
allAdd custom CSRF tokens to plugin forms if patching is delayed.
🧯 If You Can't Patch
- Restrict plugin access to trusted IP addresses only using web server rules.
- Monitor administrator sessions for unusual activity and implement strict input validation.
🔍 How to Verify
Check if Vulnerable:
Check the plugin version in WordPress admin under Plugins > Installed Plugins; if version is 2.4.1 or lower, it is vulnerable.Check Version:
wp plugin get call-now-coccoc-pht-blog --field=versionVerify Fix Applied:
After updating, confirm the plugin version is 2.4.2 or higher in the same location.📡 Detection & Monitoring
Log Indicators:
- Unusual POST requests to plugin admin endpoints, unexpected script injections in database logs.
Network Indicators:
- Traffic patterns showing CSRF attacks or XSS payload delivery to vulnerable endpoints.
SIEM Query:
source="wordpress.log" AND (plugin="call-now-coccoc-pht-blog" AND version<="2.4.1")