CVE-2025-22549

6.5 MEDIUM

📋 TL;DR

This stored cross-site scripting (XSS) vulnerability in the WP Github WordPress plugin allows attackers to inject malicious scripts into web pages. When users view pages containing the malicious content, the scripts execute in their browsers, potentially stealing credentials or performing unauthorized actions. All WordPress sites using WP Github versions up to 1.3.3 are affected.

💻 Affected Systems

Products:
  • WP Github WordPress Plugin
Versions: n/a through 1.3.3
Operating Systems: Any OS running WordPress
Default Config Vulnerable: ⚠️ Yes
Notes: Requires the WP Github plugin to be installed and active on WordPress sites.

⚠️ 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 or credentials, potentially compromising user accounts.

🟢

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 are commonly exploited, though specific exploit details for this CVE aren't publicly documented.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.3.4 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/wp-github/vulnerability/wordpress-wp-github-plugin-1-3-3-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 WP Github plugin. 4. Click 'Update Now' if update is available. 5. Alternatively, download latest version from WordPress repository and manually update.

🔧 Temporary Workarounds

Disable WP Github Plugin

all

Temporarily deactivate the vulnerable plugin until patched version is available.

wp plugin deactivate wp-github

Implement Content Security Policy

all

Add CSP headers to restrict script execution sources.

Add to .htaccess: Header set Content-Security-Policy "default-src 'self'; script-src 'self'"
Or add to WordPress functions.php: header("Content-Security-Policy: default-src 'self'; script-src 'self'");

🧯 If You Can't Patch

  • Remove WP Github plugin completely if not essential for site functionality.
  • Implement web application firewall (WAF) rules to block XSS payloads targeting this plugin.

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin → Plugins → Installed Plugins for WP Github version. If version is 1.3.3 or earlier, site is vulnerable.

Check Version:

wp plugin get wp-github --field=version

Verify Fix Applied:

After updating, verify WP Github plugin version is 1.3.4 or later in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to WP Github plugin endpoints containing script tags or JavaScript code
  • Multiple failed login attempts following suspicious plugin activity

Network Indicators:

  • Outbound connections to unknown domains from WordPress site following plugin usage
  • Unexpected JavaScript payloads in HTTP responses from WP Github endpoints

SIEM Query:

source="wordpress.log" AND "wp-github" AND ("<script>" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export