CVE-2025-31861

6.5 MEDIUM

📋 TL;DR

This stored cross-site scripting (XSS) vulnerability in the Perfect Font Awesome Integration WordPress plugin allows attackers to inject malicious scripts into web pages. When exploited, these scripts execute in victims' browsers, potentially stealing session cookies or performing actions on their behalf. All WordPress sites using vulnerable versions of this plugin are affected.

💻 Affected Systems

Products:
  • Perfect Font Awesome Integration WordPress Plugin
Versions: All versions up to and including 2.2
Operating Systems: All operating systems running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires WordPress installation with the vulnerable plugin activated.

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

Attackers could steal administrator session cookies, take over WordPress sites, deface websites, or redirect visitors to malicious sites.

🟠

Likely Case

Attackers inject malicious JavaScript to steal user session cookies, potentially compromising user accounts and performing unauthorized actions.

🟢

If Mitigated

With proper input validation and output encoding, malicious scripts would be neutralized before reaching users' browsers.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Stored XSS vulnerabilities in WordPress plugins are commonly exploited. Attackers need to inject malicious payloads through vulnerable input fields.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Version 2.3 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/perfect-font-awesome-integration/vulnerability/wordpress-perfect-font-awesome-integration-plugin-2-2-stored-cross-site-scripting-xss-vulnerability?_s_id=cve

Restart Required: No

Instructions:

1. Log into WordPress admin panel. 2. Navigate to Plugins > Installed Plugins. 3. Find 'Perfect Font Awesome Integration'. 4. Click 'Update Now' if available. 5. Alternatively, download version 2.3+ from WordPress repository and manually update.

🔧 Temporary Workarounds

Disable vulnerable plugin

all

Temporarily deactivate the Perfect Font Awesome Integration plugin until patched

wp plugin deactivate perfect-font-awesome-integration

Implement WAF rules

all

Add web application firewall rules to block XSS payloads targeting this plugin

🧯 If You Can't Patch

  • Remove the Perfect Font Awesome Integration plugin completely
  • Implement strict Content Security Policy (CSP) headers to mitigate script execution

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > Perfect Font Awesome Integration for version number. If version is 2.2 or lower, you are vulnerable.

Check Version:

wp plugin get perfect-font-awesome-integration --field=version

Verify Fix Applied:

After updating, verify plugin version shows 2.3 or higher in WordPress admin plugins page.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to plugin endpoints
  • Suspicious JavaScript payloads in request logs
  • Multiple failed login attempts following suspicious requests

Network Indicators:

  • Malicious script tags in HTTP requests to WordPress admin areas
  • Unexpected outbound connections from WordPress site

SIEM Query:

source="wordpress.log" AND ("perfect-font-awesome-integration" OR "font-awesome") AND ("script" OR "javascript" OR "onload" OR "onerror")

🔗 References

📤 Share & Export