Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Wasabee

    (@wasabee)

    Does anyone have an idea for a solution?

    Thread Starter Wasabee

    (@wasabee)

    Hi Tim,

    no, “Scan image files as if they were executable” is not checked.

    In fact my “scans to include” options look like follows:

    Scan for the HeartBleed vulnerability?
    -> checked
    Scan core files against repository versions for changes
    -> checked
    Scan theme files against repository versions for changes
    -> nope
    Scan plugin files against repository versions for changes
    -> checked
    Scan for signatures of known malicious files
    -> checked
    Scan file contents for backdoors, trojans and suspicious code
    -> checked
    Scan database for backdoors, trojans and suspicious code
    -> checked
    Scan posts for known dangerous URLs and suspicious content
    -> checked
    Scan comments for known dangerous URLs and suspicious content
    -> checked
    Scan for out of date plugins, themes and WordPress versions
    -> checked
    Check the strength of passwords
    -> checked
    Monitor disk space
    -> checked
    Scan for unauthorized DNS changes
    -> checked
    Scan files outside your WordPress installation
    -> nope
    Scan image files as if they were executable
    -> nope
    Enable HIGH SENSITIVITY scanning. May give false positives.
    -> nope
    Exclude files from scan that match these wildcard patterns. Comma separated.
    -> *.jpg,*.png

    Regards,
    Nina

    Thread Starter Wasabee

    (@wasabee)

    Hi Brian,

    thanks for your quick response.
    I’ve used 6.0.3 before and wildcards didn’t work already.
    I hoped an update would fix the problem…

    Regards,
    Nina

Viewing 3 replies - 1 through 3 (of 3 total)