CVE-2025-30874

4.3 MEDIUM

📋 TL;DR

This CVE describes a missing authorization vulnerability in the WordPress plugin 'Specific Content For Mobile' that allows attackers to bypass access controls and view restricted content. The vulnerability affects all versions up to and including 0.5.3, potentially exposing sensitive content intended only for mobile users to unauthorized viewers.

💻 Affected Systems

Products:
  • Specific Content For Mobile WordPress Plugin
Versions: n/a through 0.5.3
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Affects WordPress installations using the vulnerable plugin versions. The vulnerability exists in the plugin's access control mechanisms.

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

Unauthorized users could access sensitive content intended only for mobile users, potentially exposing confidential information or privileged content.

🟠

Likely Case

Attackers can view content that should be restricted to mobile devices only, leading to information disclosure.

🟢

If Mitigated

With proper authorization checks, only authorized mobile users can access the intended content.

🌐 Internet-Facing: HIGH - WordPress sites are typically internet-facing, and this plugin vulnerability is directly accessible via web requests.
🏢 Internal Only: LOW - The vulnerability is specific to WordPress plugin functionality and doesn't affect internal network access controls.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability involves missing authorization checks, which typically require minimal technical skill to exploit via web requests.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Versions after 0.5.3

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/specific-content-for-mobile/vulnerability/wordpress-specific-content-for-mobile-plugin-0-5-3-broken-access-control-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins → Installed Plugins. 3. Find 'Specific Content For Mobile'. 4. Click 'Update Now' if update available. 5. If no update available, deactivate and delete the plugin.

🔧 Temporary Workarounds

Disable Plugin

all

Temporarily disable the vulnerable plugin until patched version is available

wp plugin deactivate specific-content-for-mobile

Remove Plugin

all

Completely remove the vulnerable plugin

wp plugin delete specific-content-for-mobile

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block unauthorized access to plugin endpoints
  • Monitor access logs for unusual requests to the plugin's functionality

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel → Plugins → Installed Plugins for 'Specific Content For Mobile' version 0.5.3 or earlier

Check Version:

wp plugin get specific-content-for-mobile --field=version

Verify Fix Applied:

Verify plugin version is higher than 0.5.3 or plugin is removed from installed plugins list

📡 Detection & Monitoring

Log Indicators:

  • Unusual access patterns to content intended for mobile users
  • Requests to plugin-specific endpoints from non-mobile user agents

Network Indicators:

  • HTTP requests to plugin endpoints without proper authorization headers
  • Access to mobile-only content from desktop user agents

SIEM Query:

source="wordpress_access.log" AND (uri CONTAINS "/wp-content/plugins/specific-content-for-mobile/" OR user_agent NOT CONTAINS "Mobile") AND response_code=200

🔗 References

📤 Share & Export