I've actually just had this same issue with the current ColdFusion connector. The description is basically identical, just had to edit the cf_util.cfm for the CF connector. The section is:

<cffunction name="IsImageValid" returntype="boolean" output="true">
   <cfargument name="filePath" required="true" type="String">
   <cfargument name="extension" required="true" type="String">

   <cfset var imageCFC = "">
   <cfset var imageInfo = "">

   <!---
   <cfif not ListFindNoCase("gif,jpeg,jpg,png,swf,psd,bmp,iff,tiff,tif,swc,jpc,jp2,jpx,jb2,xmb,wbmp", ARGUMENTS.extension)>
      <cfreturn true>
   </cfif>
   --->
   <cfif not ListFindNoCase("gif,jpeg,jpg,png,psd,bmp,iff,tiff,tif,swc,jpc,jp2,jpx,jb2,xmb,wbmp", ARGUMENTS.extension)>
      <cfreturn true>
   </cfif>

   <cftry>
      <cfif REQUEST.CFVersion gte 8>
         <cfset objImage = ImageRead(ARGUMENTS.filePath) >
         <cfset imageInfo = ImageInfo(objImage)>
         <!--- <cfimage action="info" source="#ARGUMENTS.filePath#" structName="imageInfo" /> --->
      <cfelse>
         <cfset imageCFC = createObject("component", "image")>
         <cfset imageInfo = imageCFC.getImageInfo("", ARGUMENTS.filePath)>
      </cfif>

      <cfif imageInfo.height lte 0 or imageInfo.width lte 0>
         <cfreturn false>
      </cfif>
   <cfcatch type="any">
      <cfreturn false>
   </cfcatch>
   </cftry>

   <cfreturn true>
</cffunction>

You need to take the 'swf' option out of the file extensions it's checking. Note that I commented out the old code and just had the rest of the extensions left.

By the way, I had been searching FOREVER to find this, but had been searching for "invalid file type" rather than just "invalid file" like in the subject line. Hopefully, someone else will be able to find this now! I'll try to report the bug also.

bobhendren wrote:You need to take the 'swf' option out of the file extensions it's checking. Note that I commented out the old code and just had the rest of the extensions left.

Thank you for the information. As of version 2.6.4.1 this is still an issue and your fix worked perfectly.