CVE-2025-30892

8.8 HIGH

📋 TL;DR

This vulnerability allows attackers to inject malicious objects through deserialization of untrusted data in the WpTravelly WordPress plugin. Successful exploitation could lead to remote code execution or data manipulation. All WordPress sites using WpTravelly versions up to 1.8.7 are affected.

💻 Affected Systems

Products:
  • WpTravelly WordPress Plugin
Versions: n/a through 1.8.7
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: All WordPress installations with vulnerable WpTravelly versions are affected regardless of configuration.

⚠️ 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.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete site compromise, data theft, or server takeover.

🟠

Likely Case

Unauthenticated attackers executing arbitrary code, modifying site content, or accessing sensitive data.

🟢

If Mitigated

Limited impact if proper input validation and output encoding are implemented elsewhere.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Deserialization vulnerabilities are commonly exploited and weaponized quickly.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.8.8 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/tour-booking-manager/vulnerability/wordpress-wptravelly-plugin-1-8-7-php-object-injection-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins. 3. Find WpTravelly. 4. Click 'Update Now' if available. 5. If not, download version 1.8.8+ from WordPress repository. 6. Deactivate old version. 7. Upload and activate new version.

🔧 Temporary Workarounds

Disable WpTravelly Plugin

all

Temporarily deactivate the vulnerable plugin until patched.

wp plugin deactivate wptravelly

Restrict Plugin Access

all

Use web application firewall to block requests to vulnerable endpoints.

🧯 If You Can't Patch

  • Implement strict input validation and sanitization for all user inputs
  • Deploy web application firewall with deserialization attack detection

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > WpTravelly version. If version is 1.8.7 or lower, you are vulnerable.

Check Version:

wp plugin get wptravelly --field=version

Verify Fix Applied:

Verify WpTravelly version is 1.8.8 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to WpTravelly endpoints
  • PHP deserialization errors in logs
  • Unexpected file creation or modification

Network Indicators:

  • HTTP requests with serialized PHP objects in parameters
  • Traffic to known exploit paths

SIEM Query:

source="web_logs" AND (uri="*wptravelly*" OR uri="*tour-booking*" OR uri="*wp-content/plugins/wptravelly*") AND (method="POST" OR params="*O:*" OR params="*C:*")

🔗 References

📤 Share & Export