CVE-2023-34171

8.8 HIGH

📋 TL;DR

This CSRF vulnerability in the WP Report Post WordPress plugin allows attackers to trick authenticated users into performing unintended actions, such as submitting false reports or modifying plugin settings. It affects all WordPress sites running WP Report Post version 2.1.2 or earlier.

💻 Affected Systems

Products:
  • WordPress WP Report Post plugin
Versions: <= 2.1.2
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with vulnerable plugin version. Attack requires user to be authenticated with appropriate permissions.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could manipulate plugin settings, submit fraudulent reports, or potentially chain with other vulnerabilities to gain administrative access or deface websites.

🟠

Likely Case

Attackers trick administrators or editors into changing plugin settings or submitting false content reports, potentially disrupting site moderation.

🟢

If Mitigated

With proper CSRF protections and user awareness, impact is limited to unsuccessful attack attempts with no data compromise.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

CSRF attacks are well-understood and easy to weaponize. Exploitation requires tricking authenticated users into visiting malicious pages.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 2.1.3 or later

Vendor Advisory: https://patchstack.com/database/vulnerability/wp-report-post/wordpress-wp-report-post-plugin-2-1-2-cross-site-request-forgery-csrf-vulnerability

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'WP Report Post' and click 'Update Now'. 4. Verify update to version 2.1.3 or later.

🔧 Temporary Workarounds

Temporary Plugin Deactivation

all

Disable the vulnerable plugin until patched

wp plugin deactivate wp-report-post

CSRF Protection via Security Plugin

all

Implement additional CSRF protections using security plugins like Wordfence or Sucuri

🧯 If You Can't Patch

  • Implement strict SameSite cookie policies and Content Security Policy headers
  • Educate users about CSRF risks and safe browsing practices

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > Installed Plugins for WP Report Post version <= 2.1.2

Check Version:

wp plugin get wp-report-post --field=version

Verify Fix Applied:

Verify plugin version shows 2.1.3 or later in WordPress admin

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed report submissions from same IP
  • Unusual plugin setting changes

Network Indicators:

  • POST requests to wp-report-post endpoints without proper referrer headers

SIEM Query:

source="wordpress.log" AND "wp-report-post" AND ("POST" OR "action")

🔗 References

📤 Share & Export