Exploit Scanner vs HTTP Digest — WordPress

Exploit Scanner vs HTTP Digest Authentication

Name: Exploit Scanner
Rating: 3.2 (40 reviews)

Side-by-side comparison · 24 data points

Exploit Scanner

3.2·40reviews·8,000+installs

wordpress

Change

1. Listing metadata

Field-level data

	Exploit Scanner	HTTP Digest Authentication
Tagline	—	—
Description	3095 / 5000 chars62% used	2439 / 5000 chars49% used
Screenshots	—	—
Languages
Platforms	WordPress	WordPress
Developer	Donncha O Caoimh (a11n)	Jesin A
Listed	—	—
Last updated	—	—

2. Categories & rankings

Shared categories on the same row · in-category position inline

Exploit Scanner

HTTP Digest Authentication

Shared

At a glance

4 metrics · auto-computed

Feature comparison between Exploit Scanner and HTTP Digest Authentication
Metric	Exploit Scanner	HTTP Digest Authentication
Rating	3.2 ★	★ 4.0 ★
Total reviews	★ 40	5
Active installs	8,000+	10+
Free plan	—	—

3. App details

Long-form description · keyword frequency

Exploit Scanner

This plugin searches the files on your website, and the posts and comments tables of your database for anything suspicious. It also examines your list of active plugins for unusual filenames. It does not remove anything. That is left to the user to do. Latest MD5 hash values for Exploit Scanner: 17e2ccfc834d691bc68cc5c64f9bed89 exploit-scanner.php (1.5.2) 1d5f9d6220fe159cd44cb70a998a1cd7 hashes-4.6.php fbdf61c17f65094c8e331e1e364acf68 hashes-4.6.1.php 477d128d84802e3470cec408424a8de3 hashes-4.7.php d53210f999847fbd6f5a2ecac0ad42f2 hashes-4.7.5.php Latest SHA1 hash values for Exploit Scanner: 1decc1e47a53d1cab9e8f1ef15b31682198367ee exploit-scanner.php (1.5.2) 5cec64380a2acdc876fd22fbbbbf8c335df1ed3f hashes-4.6.php 99d9e7be23a350f3d1962d0f41e7b4e28c00841e hashes-4.6.1.php 1eeab377a1afc6d776827a063678d2461b29e71d hashes-4.7.php 8c890a6af26bb74e9d17e5d2b21d6be27764da45 hashes-4.7.5.php See the Exploit Scanner homepage for further information. Interpreting the Results It is likely that this scanner will find false positives (i.e. files which do not contain malicious code). However, it is best to err on the side of caution; if you are unsure then ask in the Support Forums, download a fresh copy of a plugin, search the Internet for similar situations, et cetera. You should be most concerned if the scanner is: making matches around unknown external links; finding base64 encoded text in modified core files or the wp-config.php file; listing extra admin accounts; or finding content in posts which you did not put there. Understanding the three different result levels: Severe: results that are often strong indicators of a hack (though they are not definitive proof) Warning: these results are more commonly found in innocent circumstances than Severe matches, but they should still be treated with caution Note: lowest priority, showing results that are very commonly used in legitimate code or notifications about events such as skipped files Help! I think I have been hacked! Follow the guides from the Codex: Codex: FAQ – My site was hacked Codex: Hardening WordPress Ensure that you change all of your WordPress related passwords (site, FTP, MySQL, etc.). A regular backup routine (either manual or plugin powered) is extremely useful; if you ever find that your site has been hacked you can easily restore your site from a clean backup and fresh set of files and, of course, use a new set of passwords. Updates Updates to the plugin will be posted here, to Holy Shmoly! and the WordPress Exploit Scanner page will always link to the newest version. Other Languages Unfortunately for people using WordPress versions for other locales some of the file hashes may be incorrect as some strings have to be hardcoded in their translated form. Here are some file hashes for WordPress in other languagues provided separately by other members of the community: Japanese – thanks to Naoko German – thanks to Robert Wetzlmayr The hash files should only be declaring an array called $filehashes and the majority of the hashes should still be the same.

Top keywords

php11×2.37%
hashes-48×1.72%
files6×1.29%
scanner6×1.29%
wordpress5×1.08%
exploit4×0.86%
exploit scanner4×0.86%
results4×0.86%
site4×0.86%
codex3×0.65%
file3×0.65%
hacked3×0.65%

HTTP Digest Authentication

This plugin adds an additional layer of protection for the wp-login.php page using HTTP Digest Authentication with the PHP header() function. So it doesn’t require configuring web server files like .htaccess or .htdigest and works on all web hosting environments. Important: If you already have a plugin which does HTTP Authentication please deactivate it before activating this plugin. Similarly if you have configured your web server to do HTTP authentication on the wp-login.php file please remove it before using this plugin. If you are using FastCGI PHP this plugin may keep prompting for the credentials even if you enter the right pair, in this case use the following in your .htaccess file SetEnvIfNoCase ^Authorization$ "(.+)" PHP_AUTH_DIGEST=$1 Advantages of HTTP Digest Authentication Digest Authentication is very much safer than HTTP Basic Authentication whose credentials can be easily decoded with a base64 decoder. From Wikipedia on HTTP Basic Authentication: The BA (Basic Authentication) mechanism provides no confidentiality protection for the transmitted credentials. They are merely encoded with BASE64 in transit, but not encrypted or hashed in any way. Digest Authentication on the other hand uses MD5 on the credentials making it “one way” Uses server and client nonces to prevent replay attacks Features of the HTTP Digest Auth plugin Works using PHP header() function and doesn’t require modification of service config files (like .htaccess, nginx.conf etc) Supports HTTP credentials for each WordPress user Clears the HTTP Digest credentials when the user logs out of WordPress (more on this in the FAQ) Verifies if both the HTTP and WordPress credentials are of the same user (this is the default behavior and can be changed) Works on all major Web Servers (Tested on Apache, Nginx and Lighttpd) Plugin Behavior When this plugin is activated for the first time all WordPress users will have the following Digest credentials Username: Password: password This can be changed from Users > Your Profile. After activating this plugin for the first time you’ll be prompted for HTTP credentials when you logout Similarly if you change your HTTP username or password you’ll be prompted for this when you logout Available languages English Serbo-Croatian by Borisa Djuraskovic The HTTP Digest Authentication Plugin official homepage.

Top keywords

http13×3.50%
authentication10×2.70%
credentials9×2.43%

Frequently asked

Common questions about this comparison

Which has better reviews, Exploit Scanner or HTTP Digest Authentication?

HTTP Digest Authentication has the higher average rating (4.0★ from 5 reviews) compared to Exploit Scanner (3.2★ from 40 reviews). Both are tracked daily by AppRanks, so the figures here update each refresh cycle.

Should I choose Exploit Scanner or HTTP Digest Authentication?

HTTP Digest Authentication holds the higher average rating (4.0★ vs 3.2★). That is the one dimension AppRanks can separate them on here — read both apps' detail pages for the feature breakdown and recent listing changes.

Which is faster to set up, Exploit Scanner or HTTP Digest Authentication?

Both apps are one-click installs from the WordPress Plugin Directory. Exploit Scanner has the deeper published review base (40 vs 5), which often — though not always — accompanies better-tested setup docs. AppRanks doesn't measure setup time directly: read the recent reviews on each app's detail page for user-reported install experience.

Which works better for small vs large WordPress Plugin Directory site owners?

Exploit Scanner typically suits early-stage and growth-mode teams based on its published review base (40 reviews). HTTP Digest Authentication typically suits early-stage and growth-mode teams based on its published review base (5 reviews). A larger review base generally means the app has been exercised at scale — relevant if you are processing high volume or handling enterprise compliance requirements.

Can I migrate data between Exploit Scanner and HTTP Digest Authentication?

Migration support varies by app and category. Exploit Scanner and HTTP Digest Authentication both publish their export options on their marketplace listing pages (or in their support docs); some apps offer one-click import from competitors, others require CSV. The fastest check: search "import from HTTP Digest Authentication" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.

Exploit Scanner vs HTTP Digest Authentication

Exploit Scanner

1. Listing metadata

2. Categories & rankings

HTTP Digest Authentication

At a glance

AppRanks verdict

3. App details

Frequently asked

Which has better reviews, Exploit Scanner or HTTP Digest Authentication?

Should I choose Exploit Scanner or HTTP Digest Authentication?

Which is faster to set up, Exploit Scanner or HTTP Digest Authentication?

Which works better for small vs large WordPress Plugin Directory site owners?

Can I migrate data between Exploit Scanner and HTTP Digest Authentication?

See full keyword rankings, install trends, and weekly alerts

More popular comparisons