Hiperlink Security

Description

Hiperlink Security is a lightweight WordPress security plugin with two-factor authentication (2FA), hardening, security headers and a security checklist, made of modules you can switch on and off under Settings > Security. It does not call any outside service, does not load anything from other sites and sets no cookies.

  • Hardening (on by default): stops user enumeration, turns off pingbacks and hides software versions. Optional: a failed login limit and password logins only on the login page.
  • Custom login address (off until you turn it on): moves the login page to an address you choose, so bots find no login form at wp-login.php.
  • Two-factor login (off until you turn it on): a code from an authenticator app after the password, with backup codes; can be required for administrators.
  • Security headers (off until you turn it on): the HTTP security headers scanners look for, and a Content Security Policy rolled out safely through Report-Only mode with CSP reports collected on your own site.
  • Site check (on by default): a WordPress security checklist with a score out of 100, on the dashboard and in its own tab.
  • Activity log (off until you turn it on): who logged in, failed logins, account security, user, plugin, theme and core changes, published and deleted content and saved settings.
  • Comments off (off until you turn it on): closes and hides comments everywhere, for sites that do not use them.
  • Form antispam (off until you turn it on): stops spam bots in the comment form, Contact Form 7, WPForms, Elementor Pro and Fluent Forms without a CAPTCHA.
  • Hide footprints (off until you turn it on): hides which plugins your site uses from visitors and scanners. It makes automated targeting harder; it does not replace updates.

Why Hiperlink Security

  • No weight for visitors: with the default modules, +0 database queries on an uncached page (about +130 KB of memory in our measurements) and no script, stylesheet or inline JavaScript. With every module on, still +0 queries.
  • Nothing leaves your site: no account or API key; 2FA QR codes are made on your server and CSP reports go to your own site.
  • Simple: one settings page with a tab for each module that has settings, and safe defaults; a module that is off is not loaded.
  • No ads, upsell notices or tracking. Deleting the plugin removes everything it stored.

Works with: WooCommerce (two-factor login and the login limit on My account and checkout), Contact Form 7, WPForms, Elementor Pro and Fluent Forms, Polylang, page caches such as Hiperlink Cache, multisite, and next to Wordfence or Solid Security (tested with all modules on).

Hardening module

Stop user enumeration

  • Author archives (/?author=1, /author/name/) return 404 for visitors who are not logged in.
  • The REST API users routes (/wp-json/wp/v2/users) are removed for visitors who are not logged in. The block editor keeps working.
  • The users sitemap and the author name in oEmbed data are removed.
  • A failed login and the lost password form give the same answer, so they no longer say whether a user name exists.
  • The tab warns about users who publish under their login name, which feeds show.

Turn off pingbacks and trackbacks

  • Publishing does not make your server connect to linked sites or ping services, so its address stays private.
  • Incoming pingbacks over XML-RPC and trackbacks are closed, and the X-Pingback header is removed.

Hide software versions

  • Removes the X-Powered-By header with the PHP version, the WordPress generator tag and the WordPress version in ?ver= of scripts, styles and script modules (a hash that still changes with each update).

Optional

  • Password logins only on the login page: xmlrpc.php refuses every login with a user name and password, so it can no longer be used to guess passwords, many at a time through system.multicall, and only administrators keep application passwords for the REST API (other users’ existing ones stop working). Off by default, because the WordPress mobile app, desktop blog editors and some Jetpack features log in through XML-RPC.
  • Limit failed logins: after 5 failed logins from one address, each within 15 minutes of the one before, that address cannot log in for 15 minutes (login form, XML-RPC, application passwords). Addresses are kept only as a keyed hash. Behind Cloudflare visitors’ addresses are read correctly; behind another proxy once you list it as trusted.
  • Remove readme.html and license.txt from the site root now and after every core update, because readme.html shows the WordPress version.
  • Polylang: no pll_language cookie, for sites that always keep the language in the URL.

Custom login address module

Bots try passwords at wp-login.php on every WordPress site. With your own address they find no login form: wp-login.php and wp-admin show visitors who are not logged in your site’s missing page, exactly as for any address that does not exist.

  • The address appears only on the login page and for logged-in users, never in pages, redirects or headers for other visitors.
  • Two-factor login, password reset and registration emails, the WooCommerce My account login, password-protected posts, the REST API and XML-RPC keep working. Page caches never save the login page.
  • Forgot it? define( 'HIPERLINK_SECURITY_LOGIN_URL_OFF', true ); in wp-config.php or wp hiperlink-security login-url off switches it off.

Two-factor login module

Two-factor authentication (2FA) for WordPress logins with an authenticator app, made entirely on your site: no SMS, no outside service, no account anywhere.

  • Authenticator apps: time-based one-time passwords (TOTP, RFC 6238) that work with Google Authenticator, Microsoft Authenticator, Authy and other apps.
  • Setup in the profile: each user scans a QR code made on your own server (the secret never goes to a QR service), or types the key, and confirms with a code.
  • 10 backup codes: each logs in once without the phone. They are stored hashed and shown only once.
  • Require it for administrators, with a grace period of up to 30 days. After it, an administrator without two-factor login sees only their profile until they set it up.
  • No way around it: the login cookie is set only after the code. XML-RPC and other logins with the password alone are refused for these users. Application passwords keep working for apps, because only a user who passed two-factor login can create one.
  • Works with the login limit: wrong codes count like wrong passwords.
  • Lost phone: another administrator resets it in the user’s profile, or the host runs wp hiperlink-security 2fa reset <user>.

Security headers module

Adds the HTTP security headers that scanners look for, with defaults that do not break WordPress, and rolls out a Content Security Policy the safe way: first in Report-Only mode with CSP reports collected on your own site, then enforced.

  • X-Content-Type-Options: nosniff, so an uploaded file cannot run as a script.
  • X-Frame-Options: SAMEORIGIN or DENY against clickjacking; with the CSP on, frame-ancestors follows it.
  • Referrer-Policy: strict-origin-when-cross-origin, a stricter value, or off.
  • Permissions-Policy: camera, microphone, geolocation, USB and ad topics off; payment stays allowed for shop wallets.
  • Strict-Transport-Security (HSTS), off by default: 5 minutes to 2 years, with clear warnings. includeSubDomains and preload are never on by default.
  • Status check: Check now requests your home page as a visitor, also past the page cache, and shows each header received next to the one sent, so you see when a CDN, the server, a cache or another plugin overrides, drops or doubles one.

Content Security Policy in four steps:

  1. Scan the home page, the newest post and page and the shop page, and build the policy from 'self' plus the outside scripts, styles, fonts, images, frames, media and form targets they load (Google Fonts and Analytics included).
  2. Report-Only: browsers report what the policy would block, without blocking anything.
  3. Allow: blocked sources are listed by directive with a count, the last time and the page. Allow trusted ones in one click, or ignore them.
  4. Enforce: one click and a confirmation send the real Content-Security-Policy header. You can go back at any time.

Every directive can also be edited by hand; invalid sources are removed, so a typo cannot break the header.

Site check module

A WordPress security checklist with a score out of 100: 22 checks run from inside your site, and each item that needs work gets one plain sentence on fixing it. The results are on the dashboard and under Settings > Security > Site check. When another module can fix an item, the result names the module.

HTTPS and security headers

  • The site address uses HTTPS, and http:// redirects to https://.
  • Security headers on the home page: Strict-Transport-Security (HSTS), X-Frame-Options or frame-ancestors, Content-Security-Policy (including report-only mode), X-Content-Type-Options and Referrer-Policy.

WordPress hardening audit

  • Pending WordPress, plugin and theme updates, read from WordPress’s own update data.
  • PHP version: whether it still gets security fixes, and for how long.
  • User enumeration through the REST API users route and ?author=1.
  • XML-RPC that accepts logins or pingbacks, and no limit on failed logins.
  • readme.html and license.txt that anyone can open.
  • Downloadable backups: wp-config.php copies, .env, .git, database dumps, archives and a listed uploads folder.
  • PHP and WordPress versions in the X-Powered-By header or the generator tag.
  • Errors shown on pages (WP_DEBUG_DISPLAY, display_errors) and a debug log inside the web root.
  • The plugin and theme code editor in the dashboard (DISALLOW_FILE_EDIT).
  • A user named “admin”, and open registration with a powerful default role.
  • Administrators without two-factor login.

Email security: SPF and DMARC

  • The SPF record of your domain and how it ends (-all, ~all, ?all or +all), following redirect=.
  • The DMARC policy (none, quarantine or reject), also on the parent domain for subdomains.

A check that cannot run, for example when the host blocks the site’s requests to itself, shows Not checked and does not count. The score averages three areas, Security, Hardening and Email; problems attackers use more often count more.

The check runs only when you press “Check now”. It asks your own site for a few pages as a visitor and reads your domain’s DNS records; nothing is sent anywhere else.

Activity log module

A WordPress activity log (audit log) that stays small:

  • What it records: logins, logouts and failed logins, password resets, password, email, two-factor and application password changes, user and role changes, plugin, theme and WordPress installs, updates and removals, published, trashed and deleted content, saved settings pages, and registration, site address and admin email changes from any source. Each entry has the time, the user, the action and what it was done to.
  • What it does not record: passwords, content, or IP addresses unless you choose to store them. A failed login with a user name that does not exist is logged without the typed name.
  • Stays small: failed logins are counted per user name and hour, so an attack adds a few rows, not thousands. Old entries go after 30 to 365 days (90 by default), and the log keeps about the newest 10,000.
  • List and export: filter by action, user and period, and download the result as a CSV file that is safe to open in a spreadsheet.

Comments off module

For sites that do not use comments. It replaces a separate “disable comments” plugin:

  • Comments, pingbacks and trackbacks are closed on every post, page and custom post type, and existing comments are no longer shown, also in block themes.
  • The Comments menu, Discussion settings, editor boxes, comment column, Recent Comments widget, dashboard widget comments and admin bar item are removed.
  • wp-comments-post.php answers 403, the REST API comments routes and the XML-RPC comment and pingback methods are removed, comment feeds answer 404 and the X-Pingback header is gone.
  • Nothing is deleted: switch the module off and the comments are back.

Form antispam module

Stops spam bots without a CAPTCHA, a cookie or an outside service, and without slowing visitors down: nothing runs in the browser.

  • Honeypot: a text field that people never see. Bots fill in every field, so a submission with something in it is refused.
  • Minimum fill time: the form carries the time it was made, signed with your site’s secret keys, so it cannot be forged or moved to another form. Bots send a form the moment they load it; anything faster than 3 seconds (or 2, 5 or 10) is refused, as are submissions without the signed time.
  • Comment form, Contact Form 7, WPForms, Elementor Pro and Fluent Forms out of the box (not Fluent Forms conversational forms). Logged-in users are not checked in the comment form, and other forms can use two filters (see the FAQ).
  • Only a count is kept: the number of blocked submissions per day for 30 days, never their content or IP addresses. Each form shows the refusal in its own way; the comment form asks to wait and send again.

Hide footprints module

Scanners such as WPScan find plugins by their readme files, folders and version numbers, then try their known holes. This makes that harder; keep updating, because a vulnerable plugin stays vulnerable.

  • Plugin files: readme, changelog, translation and build files and plugin folders answer like files that do not exist. The rules go at the top of .htaccess (Apache, LiteSpeed); for nginx the tab shows them. A check tests the result.
  • Versions: other plugins’ scripts and styles get a version that cannot be matched to a release.
  • Quiet mode: Hiperlink plugins use your site’s own names in pages, cookies and addresses (also with HIPERLINK_QUIET in wp-config.php).
  • Optional: removes other plugins’ generator tags and comments.

Nothing is hidden from administrators; turning it off undoes everything.

The plugin is made by Hiperlink Digital, a web agency from Croatia that builds, maintains and protects websites. We run the same code on our own site.

External services

Hiperlink Security uses no outside service: it sends nothing about your site, users or visitors anywhere and loads nothing from other sites.

  • Hosts in the Content Security Policy (Security headers module, off by default). When your pages already load Google Analytics, Google Tag Manager or Google Fonts, the suggested policy also allows the hosts these tools use (*.googletagmanager.com, *.google-analytics.com, *.analytics.google.com, fonts.gstatic.com). The plugin only writes these names into the header your site sends and never requests them. Whether browsers contact Google depends only on the tags or fonts you added yourself: Google terms, privacy policy.
  • Your own site and domain. Some checks open your own pages as a visitor, and Site check reads your domain’s SPF and DMARC records.
  • A link. The Site check tab links to a free outside check on hiperlink.digital; nothing is sent unless you open it.

Screenshots

Installation

  1. Install the plugin from Plugins > Add New, or upload the hiperlink-security folder to /wp-content/plugins/.
  2. Activate it. Hardening and Site check work straight away with safe defaults.
  3. Review the modules under Settings > Security, and turn on Security headers when you are ready to test the headers and the Content Security Policy.

FAQ

Does it slow down the site?

No. With the default modules, visitors’ pages make no extra database queries and load no script or style from the plugin. Modules only add a few filters, a module that is switched off is not loaded at all, and Site check runs only when you press “Check now”.

Is it free?

Yes. Every module described here is in this plugin, with no locked features and no upsell notices.

How do I add two-factor authentication to WordPress?

Turn on Two-factor login under Settings > Security. Each user then opens their profile, scans the QR code with an authenticator app such as Google Authenticator, Microsoft Authenticator or 2FAS, confirms with a code and keeps the backup codes. To make it mandatory for administrators, turn on “Require for administrators” and choose a grace period.

How do I stop user enumeration in WordPress?

The Hardening module does it as soon as you activate the plugin: author archives such as /?author=1 answer 404, the REST API users routes are hidden from visitors, and a failed login or password reset gives the same answer for every user name. Site check shows whether your site still leaks user names.

How do I add security headers in WordPress?

Turn on Security headers under Settings > Security. The basic headers (nosniff, X-Frame-Options, Referrer-Policy and Permissions-Policy) are one switch, HSTS is a separate choice, and the Content Security Policy is built from a scan of your pages and tested in Report-Only mode first. The status check shows what your home page really sends.

My theme links to author pages.

In Settings > Security > Hardening, turn off “Hide user names”. Author archives then work as before.

Does it replace a firewall or malware scanner?

No. It removes information that helps attackers, sends security headers and checks your configuration, but it does not block traffic or scan files. Keep WordPress, themes and plugins up to date and keep backups.

Can it hide which plugins my site uses?

Mostly. Turn on Hide footprints: readme files, plugin folders and version numbers stop giving plugins away, and Hiperlink plugins switch to quiet mode, with no name of ours in pages, headers, cookies, addresses or the REST API. Plugins that load scripts or styles still show their folder names in the page source, so a careful look can find them. It reduces automated targeting by bots that look for one vulnerable plugin; it does not make an outdated plugin safe, so keep updating. Quiet mode renames cookies once, so a cookie banner shows again and a login waiting for its two-factor code starts over. On nginx, add the lines the tab shows to the server block; the check on the tab tells you whether they work.

Is Site check a vulnerability scanner?

No. It does not look for malware or for known vulnerabilities in your plugins and themes. It checks settings that make attacks easier: missing HTTPS and security headers, pending updates, an old PHP version, user enumeration, XML-RPC, debug settings, downloadable backups and email records. The Updates check tells you when an update is waiting, and updates are how most vulnerabilities get fixed.

How is Site check different from Site Health?

Site Health in WordPress looks at whether the server can run WordPress well. Site check is a security audit: the headers your pages send, what visitors can learn about your users and software, and whether your domain is protected against forged email.

Some checks say “Not checked”.

Site check loads a few pages of your own site from the server. Some hosts, firewalls or local setups block those requests, and the check then says it could not run instead of guessing. SPF and DMARC are not checked for sites on an IP address or a local name. A staging copy can read the main domain’s records with the hiperlink_security_site_check_domain filter.

Will a Content Security Policy break my site?

Not while it is in Report-Only mode: browsers only report what they would block. Enforce the policy when no new reports arrive for a week or two, and go back to Report-Only if something stops working.

What is Content-Security-Policy-Report-Only?

The same policy under a different header name. Browsers check every script, style, image, font and frame against it and send a CSP report for each violation, but they load everything as usual. It is the safe way to test a policy on a live site.

Where do the CSP reports go?

To /wp-json/hiperlink-security/v1/csp-report on your own site (in quiet mode an address with your site’s own names), set as the policy’s report-uri, which Chrome, Edge, Firefox and Safari all use. Nothing is sent to us or to anyone else.

They are grouped by directive and blocked site with a count and the last time. No IP addresses, user agents, query strings or full URLs are stored. Only reports for your domain are accepted, at most 200 groups are kept and the endpoint takes at most 60 requests a minute.

Which pages get the security headers?

Public pages. Admin screens, the login page and the REST API keep WordPress’s own. The Content Security Policy goes only to visitors who are not logged in, because the admin bar and editors need more.

Why does script-src have ‘unsafe-inline’?

Most WordPress themes and plugins print small scripts inside the page, so the scan adds 'unsafe-inline' when it finds them. The policy still blocks scripts from sites it does not list, object and embed content, injected base tags and forms that send data to other sites.

A security header is missing or different.

Something between WordPress and the visitor changes the response: a page cache that serves saved HTML without PHP, a CDN or the web server that sets its own security headers, or another security plugin. Turn the header off in one of the two places so it is sent once. Site check reads the home page as a visitor without cookies, so check again after clearing the cache.

Should I turn on HSTS?

Only when the whole site works over HTTPS with a valid certificate. Browsers that see HSTS refuse plain HTTP for your domain until max-age runs out, and you cannot take that back. Start with 5 minutes or a day, then raise it to a year. Turn on includeSubDomains only when every subdomain works over HTTPS too. Behind a proxy that talks to the server over plain HTTP, set HSTS in the proxy instead.

Does it work with WooCommerce?

Yes. The header scan includes the shop page, and the Permissions-Policy leaves payment allowed for Apple Pay and Google Pay. Payment gateways load scripts and frames on the checkout page, so place a test order while the policy is in Report-Only mode and allow the gateway’s sources.

Two-factor login and the login limit also cover the WooCommerce My account and checkout login: after the password, the code is asked on the WordPress login page and the customer then returns to My account. With Hide user names on, the WooCommerce login gives the same answer for every user name and email address.

Does the login limit work behind Cloudflare or another proxy?

Yes. Behind Cloudflare the visitor’s address is read from the CF-Connecting-IP header, but only when the request really comes from one of Cloudflare’s addresses (the list is built in, and a newer one can be pasted on the Hardening tab), so nobody can choose their address by sending the header. Behind another reverse proxy or load balancer, list its addresses under Trusted proxies and the address is read from X-Forwarded-For. The tab says which applies, and warns when all visitors seem to share one address. The activity log uses the same address. Developers can also set it with the hiperlink_security_login_ip filter.

What stops working with “Password logins only on the login page”?

The WordPress mobile app, desktop blog editors and services that publish through XML-RPC stop working, and so may Jetpack features that use it, as do integrations that use a non-administrator’s application password. The block editor, the login form and administrators’ application passwords keep working. Pingbacks are a separate option.

Will Form antispam block real visitors?

Only someone who sends a form within a few seconds of opening the page, or a page that has been open, or cached, for more than 30 days. The message asks them to wait a moment or reload the page and send again. Visitors with a password manager are safe: the hidden field has no name a browser fills in. Page caches are fine too: a cached page carries an older time, which only makes the minimum easier to meet.

How do I protect another form with Form antispam?

Print the fields inside the form with echo apply_filters( 'hiperlink_security_antispam_fields', '', 'my-form' ); and refuse the submission when apply_filters( 'hiperlink_security_antispam_is_spam', false, 'my-form' ) returns true.

Does Comments off delete my comments?

No. They stay in the database, out of sight. Switch the module off and they are back where they were.

Does Comments off remove WooCommerce product reviews?

No. Reviews are comments too, but they follow WooCommerce’s own setting (WooCommerce > Settings > Products > Enable product reviews), so a shop can close blog comments and keep its reviews. Turn reviews off there if you do not want them either.

I lost my phone and cannot log in.

Use one of your backup codes. Without them, ask another administrator to reset two-factor login in your profile, or ask your host to run wp hiperlink-security 2fa reset your-user-name. As a last resort, rename the plugin folder over FTP, log in and rename it back.

Does two-factor login work with apps and the REST API?

Apps that log in with your WordPress password (through XML-RPC) are refused once two-factor login is on. Create an application password in your profile and use it in the app instead; it works with the REST API and XML-RPC.

Does it work on multisite?

Yes, with network activation or on single sites. Each site has its own modules and settings under its own Settings > Security; there is no network-wide settings screen, so set up each site where you need it (the safe defaults apply until you do). Only super admins can change the settings, because some of them change files shared by the whole network and how everyone logs in. Two-factor login is set up once per user, but asks for the code only on sites where the module is on; the login cookie works on the whole network, so turn it on on every site where those users can log in. Deleting the plugin removes its data from every site.

Does it work with page caches and CDNs?

Yes. The form antispam fields work on cached pages. Security headers reach cached pages when the page cache keeps the headers WordPress sent (Hiperlink Cache does); otherwise set them in the server or CDN. The status check requests your home page as a visitor and once more past the page cache, so it tells you when only the cached copy lacks a header (clear the cache) and when a firewall or CDN challenge answers instead of your site.

Can I use it together with Wordfence or Solid Security?

Yes. We tested Hiperlink Security with all modules on next to Wordfence, Solid Security, WooCommerce, Contact Form 7 and WPForms: no errors and no doubled headers. Use one plugin for each job: turn on two-factor login, the login limit and security headers in only one of them, or people are asked for two codes and counted twice. Those plugins can also block XML-RPC, the REST API or application passwords on their own. With all of them active, give PHP at least 256 MB of memory (WP_MEMORY_LIMIT); with 128 MB, logins ran out of memory even without Hiperlink Security.

The status check shows two Permissions-Policy headers.

Another plugin adds its own; WPForms does, for CAPTCHAs. Browsers combine all Permissions-Policy headers into one policy, so this is fine and the check shows it as OK.

Does it contact any outside service?

No. Requests go only to your own site, DNS lookups only to your own domain, and settings are stored as options in your database.

How do I change the WordPress login URL?

Turn on Custom login address under Settings > Security and save an address, for example example.com/my-door/. The login page is then there, and wp-login.php and wp-admin show your missing page to visitors who are not logged in. Bookmark the new address. Links to wp-login.php in your theme, such as a “Log in” link or the one in the comment form, lead to the missing page too.

I forgot my login address.

Add define( 'HIPERLINK_SECURITY_LOGIN_URL_OFF', true ); to wp-config.php, above “That’s all, stop editing!”, and log in at wp-login.php; remove the line afterwards. With WP-CLI, wp hiperlink-security login-url show prints the address and wp hiperlink-security login-url off switches the module off.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Hiperlink Security” is open source software. The following people have contributed to this plugin.

Contributors

Translate “Hiperlink Security” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.1.18

  • Custom login address (security fix): some variations of the wp-login.php address could still show the login form to visitors. wp-login.php now decides as WordPress does, so they get the missing page.
  • Custom login address: the link in WordPress’s recovery mode email works again. It stays on wp-login.php, where WordPress checks it, and after it wp-login.php sends you on to the login address.
  • Hide footprints: turning it off and another module on in the same save no longer leaves quiet mode on for the other Hiperlink plugins.
  • Site Check: an HSTS max-age of 180 days, the Headers module’s “6 months”, now passes. A server that drops xmlrpc.php or http:// without an answer no longer hides the whole score. HTTPS is read from the saved Site Address, not from the scheme of the dashboard you opened. On a network, SPF and DMARC are read for the domain WordPress sends mail from.
  • Hardening: with “Hide user names”, an unknown name on the lost password form gets exactly the redirect a real account gets.
  • Comments off: WooCommerce review moderation (Approve, Trash and Spam in the email, Edit under Products > Reviews) works again.
  • Two-factor login: its user meta is protected, so REST APIs that list user meta, such as WooCommerce’s customers endpoint, leave the secret out.
  • Readme: on a network, two-factor login asks for the code only on sites where the module is on.

1.1.17

  • Site Check: the “Login names” check no longer warns when ?author= redirects to the home page of a domain whose name equals the author slug (for example the user “example” on example.com). Only a redirect whose path contains the slug, such as /author/example/, counts as showing the login name.

1.1.16

  • Site Check: a new check, “Registration of new users”, fails when anyone can register and the default role can change the site, its users or other people’s content (a common change after a break-in), and warns when that role can publish posts or upload files.
  • Site Check: a new check, “Limit on failed logins”, warns when nothing on the site limits password guessing and names Hardening > Limit failed logins. With Wordfence, Solid Security, Limit Login Attempts Reloaded, Loginizer or All-In-One Security it says to check the limit there.
  • Activity log: records changes to “Anyone can register”, the default role, the WordPress and site addresses and the admin email, whoever makes them (Settings > General, WP-CLI or a plugin), with the old and new value. The admin email address itself is not stored.

1.1.15

  • Site Check: a new check, “Backups and hidden files”, fails when anyone can download a copy of wp-config.php, a .env file, the .git folder, a database dump or an archive from the site folder, and warns when the uploads folder lists its files. It requests only files that exist, compares what it gets with the file itself, and sends nothing elsewhere.

1.1.14

  • Code review for WordPress.org: PHP 7.4 no longer relies on the PHP 8 string functions WordPress adds, every output is escaped where it is printed, settings name their sanitizing functions in full, translations come from translate.wordpress.org, and the readme has an “External services” section (the plugin uses none).
  • Site Check: a new check, “Two-factor login for administrators”, warns when administrators log in with the password alone. It reads the Two-factor login module and the Two Factor plugin; with Wordfence Login Security or Solid Security it says to check there.
  • Activity log: the CSV export no longer adds a PHP deprecation notice for every row on PHP 8.4 and newer, and quotes values as spreadsheets expect (RFC 4180), also when a title contains a backslash.
  • Comments off: WooCommerce product reviews keep working and follow WooCommerce’s own “Enable product reviews” setting. Before, the module also removed the reviews tab, the review form and every review on product pages.
  • Activity log: records account security changes: a new password or email address saved in a profile, two-factor login turned on or off (also when an administrator or WP-CLI resets it), new backup codes, and application passwords created or revoked. Passwords and email addresses themselves are never stored.
  • Site Check: “Visible software versions” also finds the WordPress version in the addresses of scripts and styles (?ver=), not only the generator tag and the X-Powered-By header.
  • Hardening, Hide versions: script modules (WordPress 6.5+) without a version of their own no longer show the WordPress version in their address and in the import map; they get the same hash as scripts and styles.
  • Two-factor login in the dashboard’s “session expired” window: the code step stays in the window and, after the code, the window closes like after a normal login. Before, the dashboard opened inside the window, and an expired code step showed the full login page there.
  • Two-factor login: after the code, users go where a login without it sends them. Administrators see WordPress’s check of the admin email every 6 months, and users who cannot edit posts (subscribers, shop customers) go to their profile instead of the dashboard.
  • Custom login address: after you save a new address, the site opens it once as a visitor. If the server answers with its own missing page (for example Apache with plain permalinks), the old address is kept, so nobody gets locked out after logging out.
  • Custom login address: a page or post saved later at the login address gets the next free address instead of never showing.
  • Custom login address: a made-up or expired login cookie no longer changes the missing page in wp-admin.
  • Custom login address: wp-login.php and wp-admin now answer exactly like the site’s other missing pages, with the headers themes and plugins send (security headers, the REST API link), the page head SEO plugins add (Rank Math) and, with classic themes on WordPress 6.9+, the same styles in the head. Before, those differences showed that the missing page was not a real one.
  • Custom login address on a network in folders: a new site cannot be named like the main site’s login address, and the main site cannot choose the address of an existing site.
  • Hide footprints: plugins’ script modules (import maps, WordPress 6.5+) also get the per-site hash instead of their version.
  • Hide footprints on a network: one site turning the module off no longer removes the .htaccess lines you added for every site; uninstalling still removes them.
  • Hide footprints on nginx: the lines to copy are now rewrite lines that work anywhere in the server block. Before, they had to go above the host’s own PHP block, and where a host adds custom lines after it (Enhance, for one), the PHP files of Hiperlink plugins still answered. Translation .php files now answer like a missing .php file.
  • Activity log: when its table is gone although the settings say it is there (a site moved or restored without it, or a database cleanup removed it), the first event makes it again and is logged. Before, nothing more was logged and each event added a database error to the PHP log.

1.1.13

  • Activity log: posts published, trashed or deleted in one request are written when it ends, and six or more of a kind share one row with their count and the first titles. A bulk edit of 500 posts now adds 2 rows instead of 1,000 and about 1,000 fewer database queries, so it no longer pushes older events out of the log.
  • Form antispam: Fluent Forms are protected too (except conversational forms), with the same message as Fluent Forms’ own honeypot and nothing added to saved entries.
  • Site check: no score when the site could not load its own pages (some hosts block this), because the checks that could not run would make the score look better than it is.
  • New Hide footprints module (off until you turn it on): readme, changelog, translation and build files and the folders of every plugin answer like files that do not exist (rules at the top of .htaccess on Apache and LiteSpeed, lines to copy for nginx, and a check that compares each address with one of a plugin that is not installed); other plugins’ ?ver= becomes a hash that cannot be matched to a release; optionally, other plugins’ generator tags and comments are removed from pages. It turns on quiet mode for every Hiperlink plugin and shows which ones support it. Turning it off, deactivating or deleting the plugin undoes everything.
  • Quiet mode (with Hide footprints, or define( 'HIPERLINK_QUIET', true ); in wp-config.php): the CSP report address, the antispam field names and the two-factor login step use names of the site’s own, and the report route is left out of the /wp-json/ index. Forms from pages cached before the switch still send.
  • Hide software versions: the WordPress version in ?ver= of core scripts and styles becomes a hash that still changes with each update; on the login page core files load one by one, because the joined files carry the version without a way to change it.
  • Elementor Pro forms: the error key sent back to the browser follows quiet mode.
  • New Custom login address module (off until you turn it on): the login page moves to an address you choose, and wp-login.php and wp-admin give visitors who are not logged in exactly the page of an address that does not exist. The address shows only on the login page and to logged-in users. Two-factor login (also from the WooCommerce My account login), password reset and registration, password-protected posts, privacy request emails, the REST API, XML-RPC, admin-ajax.php and admin-post.php keep working, and page caches never save the login page. To get back in: HIPERLINK_SECURITY_LOGIN_URL_OFF in wp-config.php, or wp hiperlink-security login-url off.
  • Limit failed logins and the activity log behind Cloudflare: the visitor’s address comes from CF-Connecting-IP when the request comes from Cloudflare’s addresses (built in; a newer list can be pasted on the Hardening tab). Behind other proxies it comes from X-Forwarded-For once you list them under Trusted proxies. The Hardening tab says which applies. Before, everyone behind one Cloudflare server shared one address, and five wrong passwords locked them all out.
  • Settings of a module that was installed or switched on through WP-CLI or a script are saved on first use, so later requests no longer ask the database for them. The activity log creates its table on the first event in that case, and reports a missing table instead of assuming it exists.
  • Tested with PHP 8.5, and two-factor login from the WooCommerce checkout login and the Login/out block’s form.

1.1.12

  • Readme: a shorter summary, why the plugin stays light, what it works with, and answers on adding two-factor authentication, stopping user enumeration and adding security headers. No code changes.

1.1.11

  • Simpler Security headers screen: one switch for the basic headers, HTTPS only (HSTS) with its warning, the single header choices under Advanced, and one Save changes button. The Content Security Policy sits under its own Advanced section and shows only the next step; Enforce appears only after Report-Only and asks once, and clearing reports asks once.
  • Admin screens no longer request the site itself while they open: Security headers and Site check show the last result with a Check now button. When the site cannot load its own pages, the reason is shown once in plain words.
  • Shorter module descriptions, “Turn on” next to each module, “(no settings)” where a module has none, and a link to a module’s settings right after you turn it on.
  • Two-factor login: the set-up box has its own Turn on button and comes back to the box after saving.
  • Only what applies to the site: Form antispam lists only the forms the site has, and the Polylang option shows only with Polylang.
  • Site Check is now called Site check; “Save changes” on every settings form; links to the screens that results mention. The box about our outside website check is now one plain link at the bottom of Site check.

1.1.10

  • Multisite: a site where the plugin was never set up (after network activation, or a site added later) saves its default settings on its first visit, so its pages no longer ask the database for them on every request.
  • Readme: on a network, settings are per site; there is no network-wide settings screen.

1.1.9

  • Security: two-factor login could be skipped through XML-RPC system.multicall by someone who knew the password and had an application password for any other account. Only the user’s own application password skips the code now.
  • Two-factor login: each account allows 10 wrong codes in 15 minutes over all login attempts, also with the login limit off; a try is counted before the code is checked.
  • Two-factor login: turning it off or making new backup codes needs a current code from the app or a backup code.
  • Security headers: CSP reports with a source longer than a host name are dropped, nothing is stored while the CSP is off, and Allow is no longer the main button for script directives or sources that allow a whole kind of address.
  • Deleting the plugin on a multisite network removes its data from every site.

1.1.8

  • Form antispam: Elementor Pro forms are protected too, with the error shown in the form.
  • Form antispam, two-factor login and the login limit: the texts visitors see (the hidden field’s label for screen readers, error messages in the WooCommerce or Elementor forms) are in the site’s language.
  • Site Check: when WordPress could not reach WordPress.org to check for updates (a firewall or a host that blocks outgoing requests), Updates shows “Not checked” instead of “Passed”.

1.1.7

  • Two-factor login works from the WooCommerce My account and checkout login and other login forms: after the password, the code is asked on the login page, then the visitor returns where they were.
  • Hide user names: the WooCommerce login gives the same answer for every user name and email address too.
  • Security headers: a second Permissions-Policy header from another plugin (WPForms adds one for CAPTCHAs) is no longer reported as sent twice, because browsers combine them.
  • Lighter: pages load only the part of the Security headers module that sends the policy.
  • Clearer two-factor login messages, backup codes shown as a list, a number keypad for the code on phones, and a caption for screen readers in the activity log.

1.1.6

  • Security headers: the status check tells a page cache that still serves a copy saved before a header was added apart from a header the server or CDN drops, names the cache or CDN that answered, and says so when a firewall or CDN challenge answered instead of your site.
  • Security headers: HSTS is sent whenever the site address starts with https://, also behind a proxy or load balancer that does not pass HTTPS on to PHP.
  • Site Check: SPF and DMARC are read for the domain WordPress sends email from, for example the From address an SMTP plugin sets.
  • Multisite: only super admins can open and change Settings > Security, because some settings change shared files and how everyone on the network logs in.

1.1.5

  • New Activity log module: logins, failed logins (counted per hour), user, role, plugin, theme and core changes, published and deleted content and saved settings, in a table of its own that removes old entries; a list with filters and CSV export. IP addresses only if you choose.

1.1.4

  • New Two-factor login module: TOTP codes from an authenticator app (RFC 6238) with a QR code made on your server, 10 hashed backup codes, an option to require it for administrators with a grace period, resets by an administrator or with WP-CLI. XML-RPC logins with the password alone are refused for users with two-factor login; wrong codes count towards the login limit.

1.1.3

  • New Comments off module: comments, pingbacks and trackbacks closed and hidden everywhere (dashboard, admin bar, editor, widgets, blocks, REST API, XML-RPC, feeds); existing comments are kept.
  • New Form antispam module: a honeypot and a signed minimum fill time for the comment form, Contact Form 7, WPForms and other forms through two filters. No CAPTCHA, scripts or cookies; works with page caches; only a count of blocked submissions is kept.

1.1.2

  • Hardening: new options to limit failed logins and to allow password logins only on the login page (XML-RPC refuses logins, application passwords only for administrators). Both are off until you turn them on.
  • Lighter: visitors’ requests no longer ask the database for the plugin’s settings (they are saved with autoload on activation or when the dashboard opens), and the settings screens and Site Check’s checks load only in the dashboard and WP-CLI.
  • Croatian translation of the module list and the Hardening module.
  • Site Check: an XML-RPC finding points to the option that fixes it (logins or pingbacks), and the security header findings point to the Security headers module.
  • Site Check run from WP-CLI no longer reports the command line’s PHP version as the site’s: it keeps the version found by the last check from the dashboard.

1.1.1

  • New Security headers module: nosniff, X-Frame-Options, Referrer-Policy, Permissions-Policy and HSTS, and a Content Security Policy with Report-Only mode, CSP reports on your own site and one-click allow. Off until you turn it on.
  • New Site Check module: a security checklist with a score in three areas, on the dashboard and in its own tab, with a hint to the module that fixes an item. Croatian translation.

1.1.0

  • Renamed from Hiperlink Hardening to Hiperlink Security, with modules that can be switched on and off. The hardening features are the first module.

1.0.1

  • The lost password form gives the same answer for unknown user names, so it no longer confirms which names exist.
  • The settings page lists users who publish under their login name.

1.0.0

  • First public version (as Hiperlink Hardening).