Skip to content

Add vpatch-CVE-2025-1661 rule and test#1765

Open
crowdsec-automation wants to merge 4 commits intomasterfrom
1776258809-vpatch-CVE-2025-1661
Open

Add vpatch-CVE-2025-1661 rule and test#1765
crowdsec-automation wants to merge 4 commits intomasterfrom
1776258809-vpatch-CVE-2025-1661

Conversation

@crowdsec-automation
Copy link
Copy Markdown
Contributor

This rule detects exploitation attempts for CVE-2025-1661, an unauthenticated local file inclusion (LFI) vulnerability in the HUSKY Products Filter Professional for WooCommerce WordPress plugin. The attack is performed by sending a POST request to /wp-admin/admin-ajax.php with the template parameter containing directory traversal sequences (e.g., ../../..).

  • The first rule condition matches requests to the vulnerable endpoint /wp-admin/admin-ajax.php, using lowercase and urldecode transforms to ensure normalization and case insensitivity.
  • The second rule condition targets the template argument in the query string, again normalizing with lowercase and urldecode, and matches if it contains the directory traversal pattern '../'.
  • This approach minimizes false positives by focusing only on the relevant parameter and pattern, as per best practices for LFI detection.

The test config and nuclei template simulate the attack and expect a 403 response, confirming the rule's blocking behavior.

Validation Checklist:

  • All value: fields are lowercase.
  • All relevant transforms include lowercase and urldecode.
  • No match.value contains capital letters.
  • The rule uses contains instead of regex for the traversal pattern.

@github-actions
Copy link
Copy Markdown

Hello @crowdsec-automation and thank you for your contribution!

❗ It seems that the following scenarios are not part of the 'crowdsecurity/appsec-virtual-patching' collection:

🔴 crowdsecurity/vpatch-CVE-2025-1661 🔴

@github-actions
Copy link
Copy Markdown

Hello @crowdsec-automation and thank you for your contribution!

I'm a bot that helps maintainers to validate scenarios and ensure they include all the required information.
I've found some errors in your scenarios, please fix them and re-submit your PR, or ask for help if you need it.

The following items have errors:

crowdsecurity/crs-exclusion-plugin-cpanel:

  • labels not found

crowdsecurity/crs-exclusion-plugin-dokuwiki:

  • labels not found

crowdsecurity/crs-exclusion-plugin-drupal:

  • labels not found

crowdsecurity/crs-exclusion-plugin-nextcloud:

  • labels not found

crowdsecurity/crs-exclusion-plugin-phpbb:

  • labels not found

crowdsecurity/crs-exclusion-plugin-phpmyadmin:

  • labels not found

crowdsecurity/crs-exclusion-plugin-wordpress:

  • labels not found

crowdsecurity/crs-exclusion-plugin-xenforo:

  • labels not found

Mitre ATT&CK

Information about mitre attack can be found here.
As an example, some common mitre attack techniques:

  • T1110 for bruteforce attacks
  • T1595 and T1190 for exploitation of public vulnerabilities
  • T1595 for generic scanning of exposed applications

Expected format is (where XXXX is the technique ID):

labels:
  classification:
    - attack.TXXXX

CVEs

If your scenario covers a specific CVE (Common Vulnerabilities and Exposures), please add it.

Expected format is (where CVE-XXX-XXX is the CVE ID):

labels:
  classification:
    - cve.CVE-XXX-XXX

Behaviors

Please identify the behavior(s) your scenario is targeting. You can find the list of available behaviors here.

Expected format is (where <behavior> is the behavior you want to target):

labels:
  behavior: <behavior>

See the labels documentation for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants