Published By vs WP Author Security — WordPress

Published By vs WP Author Security

Name: Published By
Rating: 5 (1 reviews)

Side-by-side comparison · 24 data points

Published By

5.0·1reviews·50+installs

wordpress

Change

1. Listing metadata

Field-level data

	Published By	WP Author Security
Tagline	—	—
Description	1553 / 5000 chars31% used	2714 / 5000 chars54% used
Screenshots	—	—
Languages
Platforms	WordPress	WordPress
Developer	Scott Reilly	mgm security partners GmbH
Listed	—	—
Last updated	—	—

2. Categories & rankings

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

Published By

WP Author Security

Shared

At a glance

4 metrics · auto-computed

Feature comparison between Published By and WP Author Security
Metric	Published By	WP Author Security
Rating	5.0 ★	5.0 ★
Total reviews	1	★ 2
Active installs	50+	400+
Free plan	—	—

3. App details

Long-form description · keyword frequency

Published By

This plugin records which user actually published a post, which in a multi-author environment may not always be the original post author. This helps to maintain accountability for who was ultimately responsible for a post appearing live on a site. The admin listing of posts is amended with a new “Published By” column that shows the name of the person who published the post (for those posts that have actually been published). A dropdown above admin post listings allows for the listing to be filtered by a particular publishing user (but only includes posts with a known publishing user). For posts that were published prior to the use of this plugin (and thus the plugin could not directly record who published those posts), the plugin makes a best guess attempt to ascertain who published the post. After failing to find the publisher of the post as recorded by the plugin, it checks for who last edited the post, then who is responsible for the latest revision of the post, and finally failing those, it assumes it was the post author. In cases where it had to go through this process, the name of the person it deduced as the likely publisher appears italicized and with a question mark at the end. If you’d rather the plugin not make an attempt to guess the publisher, you can disable the checks by including this snippet in your theme’s functions.php (or, ideally, a site-specific mu-plugin): Links: Plugin Homepage | Plugin Directory Page | GitHub | Author Homepage

Top keywords

post10×3.94%
published7×2.76%
posts5×1.97%
author3×1.18%
publisher3×1.18%
user3×1.18%
actually2×0.79%
admin2×0.79%
attempt2×0.79%
checks2×0.79%
failing2×0.79%
guess2×0.79%

WP Author Security

WP Author Security is a lightweight but powerful plugin to protect against user enumeration attacks on author pages and other places where valid user names can be obtained. By default, WordPress will display some sensitive information on author pages. The author page is typically called by requesting the URI https://yourdomain.tld/?author= or with permalinks https://yourdomain.tld/author/ . The page will include (depending on your theme) the full name (first and last name) as well as the username of the author which is used to log in to WordPress. In some cases, it is not wanted to expose this information to the public. An attacker is able to brute force valid IDs or valid usernames. This information might be used for further attacks like social engineering attacks or log in brute force attacks with gathered usernames. However, when using the plugin and you disable author pages completely it must be noted that you need to take care that your active theme will not display the author name itself on posts like “Posted by admin” or something like that. This is something the plugin will not handle (at the moment). By using the extension, you are able to disable the author pages either completely or display them only when the author has at least one published post. When the page is disabled the default 404 error page of the active theme is displayed. In addition, the plugin will also protect other locations which are commonly used by attackers to gather valid user names. These are: The REST API for users which will list all users with published posts by default. https://yourdomain.tld/wp-json/wp/v2/users The log in page where different error messages will indicate whether an entered user name or mail address exists or not. The plugin will display a neutral error message independently whether the user exists or not. The password forgotten function will also allow an attacker to check for the existence of a user. As for the log in page the plugin will display a neutral message even when the user does not exists. Requesting the feed endpoint /feed of your blog will also allow others to see the username or display name of the author. The plugin will remove the name from the result list. WordPress supports so-called oEmbeds. This is a technique to embed a reference to a post into another post. However, this reference will also contain the author name and a direct link to the profile page. The plugin will also remove the name and link here. Since WordPress 5.5 a default sitemap can be reached via /wp-sitemap.xml. This sitemap will disclose the usernames of all authors. If this should not be disclosed you are able to disable this feature of WordPress.

Top keywords

author13×2.80%
name

Frequently asked

Common questions about this comparison

Which has better reviews, Published By or WP Author Security?

Published By (5.0★, 1 reviews) and WP Author Security (5.0★, 2 reviews) are essentially tied on rating. Look at review velocity and individual reviewer quotes — both visible on each app's detail page — to differentiate.

Should I choose Published By or WP Author Security?

AppRanks cannot separate these two on rating — both sit at 5.0★. WP Author Security does carry the larger published review base (2 vs 1). Read both apps' detail pages for the feature breakdown and recent listing changes.

Which is faster to set up, Published By or WP Author Security?

Both apps are one-click installs from the WordPress Plugin Directory. WP Author Security has the deeper published review base (2 vs 1), 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?

Published By typically suits early-stage and growth-mode teams based on its published review base (1 reviews). WP Author Security typically suits early-stage and growth-mode teams based on its published review base (2 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 Published By and WP Author Security?

Migration support varies by app and category. Published By and WP Author Security 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 Published By" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.

Published By vs WP Author Security

Published By

1. Listing metadata

2. Categories & rankings

WP Author Security

At a glance

AppRanks verdict

3. App details

Frequently asked

Which has better reviews, Published By or WP Author Security?

Should I choose Published By or WP Author Security?

Which is faster to set up, Published By or WP Author Security?

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

Can I migrate data between Published By and WP Author Security?

See full keyword rankings, install trends, and weekly alerts

More popular comparisons