• Resolved swissspaceboy

    (@swissspaceboy)


    [Feature Request] Allow excluding individual files from Activity Report “Recently Modified Files” section

    Summary:
    Currently, Wordfence only allows excluding directories from the Activity Report’s “Recently Modified Files” section. There is no way to exclude individual files. This is a limitation when developers have legitimate files (like configuration or cache files) that are modified daily at the root or other locations.

    Current Behavior:

    • Activity Report exclusion field: Only accepts directories
    • Wordfence > All Options > Activity Report > “List of directories to exclude from recently modified file list”
    • Cannot exclude a single file like /llms.txt at the WordPress root

    Desired Behavior:

    • Allow excluding individual files by their full path (e.g., llms.txt, wp-content/cache/file.txt)
    • Support the same wildcard patterns already supported in Scan Options exclusions
    • This would reduce noise in Activity Report emails for developers with expected file modifications

    Use Case:
    I have a file llms.txt at the WordPress root that is legitimately modified every day as part of my development workflow. This file appears in every Activity Report email, cluttering the report with false positives.

    Why This Makes Sense:
    The Scan Options already support file-level exclusion with full paths and wildcards (e.g., wp-content/uploads/image.jpg or wp-content/uploads/*). The same functionality would be valuable in Activity Reports for excluding specific files that change frequently but are not security concerns.

    Steps to Reproduce:

    1. Have a file at any location that is modified frequently but is legitimate
    2. Go to Wordfence > All Options > Activity Report
    3. Try to exclude just that file — only directories are supported
    4. The file continues to appear in Activity Report emails

    Expected Result:
    A field that accepts individual file paths or patterns, similar to the Scan Options exclusion field.

    Thanks,

    Didier.

Viewing 1 replies (of 1 total)
  • Plugin Support wfmargaret

    (@wfmargaret)

    Hi Didier,

    Thank you for reaching out and for the detailed feedback! I’ve passed your request for file-level exclusions on to the team. All feature requests are discussed by the team and given careful consideration, so you may possibly see this in a future version of Wordfence. I can’t share a specific timeline or commit to whether or when this will be implemented, but it’s on the team’s radar now.

    Thanks,
    Margaret

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.