Errors & Troubleshooting

Unable to Include Potential Exe - ModSecurity Error

Updated November 2026 18,413 views 3 min read
Errors & Troubleshooting | Updated November 2026

The error "Unable to include potential exe" is a ModSecurity false positive. It means the server's web application firewall detected something in your request that looks like an attempt to include an executable file, and blocked it. This commonly happens when uploading files, submitting forms with certain content, or using CMS features that pass file paths in URLs.

01. What This Error Means

ModSecurity is a web application firewall (WAF) that runs on the server to protect all websites from attacks like SQL injection, cross-site scripting, and remote file inclusion. The "unable to include potential exe" rule is designed to block attempts to include executable files from remote or local sources, which is a common attack technique.

The problem is that this rule sometimes triggers on legitimate requests. If your URL, form data, or uploaded file happens to contain patterns that look like file inclusion attempts (paths with extensions like .exe, .dll, .bat, or even some .php patterns), ModSecurity blocks it.

02. Common Triggers

  • File uploads - uploading files with executable extensions through a CMS or web form
  • WordPress plugins - some plugins pass file paths in URLs or POST data that trigger the rule
  • Form submissions - forms that contain text resembling file paths (e.g., a support form where someone pastes a Windows file path)
  • File manager plugins - web-based file managers that manipulate file paths through HTTP requests
  • Import/export features - CMS import tools that reference file names in the request

03. How to Fix It

  1. Find the error details - go to cPanel > Errors and look for the ModSecurity entry. It will include a rule ID number (like 950005 or similar) and show which part of the request triggered it
  2. Open a support ticket - include the full error log entry. We need the rule ID and the URI/parameter that triggered it
  3. We add a targeted exception - we whitelist that specific rule for your account or for the specific URL that triggers it. This keeps all other ModSecurity protections active
Warning

Do not ask to disable ModSecurity entirely. It protects your site from real attacks. We can surgically exclude the specific rule that's causing the false positive while keeping everything else active. See our 403 Error Guide for more on ModSecurity troubleshooting.

Getting This Error?

Copy the error log entry from cPanel > Errors and include it in your ticket. We typically resolve ModSecurity exceptions within a few hours.

Open a Support Ticket

Frequently Asked Questions

What does Unable to include potential exe mean?

It is a ModSecurity false positive. The server web application firewall saw something in your request that looked like an attempt to include an executable file and blocked it with this message. It commonly fires on file uploads, certain form submissions, or CMS features that pass file paths in the URL.

How do I fix the Unable to include potential exe error?

Identify the exact request that triggered it, then open a ticket with the URL and the time so the specific ModSecurity rule can be reviewed and a false positive whitelisted for your account. Avoid passing file paths or names that resemble executables in query strings where possible.

Is this error a sign my site was hacked?

Usually not. It most often blocks a legitimate action that merely resembled a risky pattern. Still, review what triggered it to be sure it was your own activity, and if it blocks a normal site feature, ask support to tune the rule.

Can I disable ModSecurity to get around this?

Disabling ModSecurity removes important protection, so the better fix is to whitelist the specific rule that false-positives while keeping the firewall on. Contact support with the blocked request details and we can tune the rule rather than turning off security.

Quick Recap

  1. This is a ModSecurity false positive - the firewall thinks your request is an attack
  2. Check cPanel > Errors - find the rule ID and full error details
  3. Open a support ticket - include the error log entry
  4. We add a targeted exception - keeps security active for everything else
  5. Don't disable ModSecurity - it protects your site from real threats

Last updated November 2026 · Browse all Troubleshooting articles · See also: 403 Errors

Share: X in Reddit f Email
  • 146 Users Found This Useful

Was this answer helpful?

Related Articles

How do I customize error messages for my site?

Errors & Troubleshooting | Updated November 2026 When visitors hit a 404 (page not...

530 Login Authentication Failed When Connecting Over FTP

FTP | Updated November 2026 The "530 Login authentication failed" error in FileZilla and...

ERR_TOO_MANY_REDIRECTS: Fixing the Redirect Loop After Enabling SSL or Cloudflare

SSL & HTTPS | Updated November 2026 The "ERR_TOO_MANY_REDIRECTS" error (also shown as...

FileZilla GnuTLS Error and Could Not Connect to Server Over FTPS

FTP | Updated November 2026 A "GnuTLS error" or "Could not connect to server" message in...



Save 30% on web hosting - Use coupon code Hosting30