CVE-2025-28870

6.5 MEDIUM

📋 TL;DR

This DOM-based Cross-Site Scripting (XSS) vulnerability in amoCRM WebForm allows attackers to inject malicious scripts into web pages viewed by other users. It affects WordPress sites using the amoCRM WebForm plugin versions up to 1.1. Attackers can steal session cookies, redirect users, or perform actions on their behalf.

💻 Affected Systems

Products:
  • amoCRM WebForm WordPress Plugin
Versions: n/a through 1.1
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects WordPress installations with the amoCRM WebForm plugin installed and active.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers steal administrator session cookies, gain full control of WordPress site, install backdoors, deface website, or steal sensitive customer data from CRM forms.

🟠

Likely Case

Attackers steal user session cookies, redirect users to phishing sites, or perform limited actions within the user's context on the affected site.

🟢

If Mitigated

With proper Content Security Policy (CSP) headers and input validation, impact is limited to script execution within the specific vulnerable component only.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

DOM-based XSS typically requires user interaction but can be exploited via crafted links or forms.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.2 or later

Vendor Advisory: https://patchstack.com/database/wordpress/plugin/amocrm-webform/vulnerability/wordpress-amocrm-webform-plugin-1-1-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 'amoCRM WebForm' and click 'Update Now'. 4. Verify version is 1.2 or higher.

🔧 Temporary Workarounds

Disable Plugin

all

Temporarily disable the vulnerable plugin until patched

wp plugin deactivate amocrm-webform

Implement CSP Headers

all

Add Content Security Policy headers to limit script execution

Add to .htaccess: Header set Content-Security-Policy "default-src 'self'; script-src 'self'"
Add to nginx config: add_header Content-Security-Policy "default-src 'self'; script-src 'self'";

🧯 If You Can't Patch

  • Disable the amoCRM WebForm plugin completely
  • Implement web application firewall (WAF) rules to block XSS payloads

🔍 How to Verify

Check if Vulnerable:

Check WordPress admin panel > Plugins > amoCRM WebForm version. If version is 1.1 or lower, you are vulnerable.

Check Version:

wp plugin get amocrm-webform --field=version

Verify Fix Applied:

Verify plugin version is 1.2 or higher in WordPress admin panel.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST/GET requests to amoCRM WebForm endpoints with script tags
  • Multiple failed login attempts following suspicious form submissions

Network Indicators:

  • HTTP requests containing <script> tags or javascript: URIs to plugin endpoints
  • Outbound connections to suspicious domains following form submissions

SIEM Query:

source="web_server" AND (uri_path="/wp-content/plugins/amocrm-webform/" AND (request_body CONTAINS "<script>" OR request_body CONTAINS "javascript:"))

🔗 References

📤 Share & Export