Skip to content
WordPress.org
  • Showcase
  • Plugins
  • Themes
  • Hosting
  • News
    • Learn WordPress
    • Documentation
    • Education
    • Forums
    • Developers
    • Blocks
    • Patterns
    • Photos
    • Openverse ↗︎
    • WordPress.tv ↗︎
    • About WordPress
    • Make WordPress
    • Events
    • Five for the Future
    • Enterprise
    • Gutenberg ↗︎
    • Job Board ↗︎
  • Swag ↗︎
  • Get WordPress
Get WordPress
WordPress.org

Plugin Directory

DROVNE Rocca

  • Submit a plugin
  • My favorites
  • Log in
  • Submit a plugin
  • My favorites
  • Log in

DROVNE Rocca

By DROVNE
Download
  • Details
  • Reviews
  • Installation
  • Development
Support

Description

DROVNE Rocca protects a WordPress site with a few focused tools. Each one has its own switch, and the plugin never contacts an outside server.

Login protection

  • Locks out an IP address after too many failed logins on the login form, XML-RPC and application passwords. Repeated lockouts within a day last hours instead of minutes.
  • An allowlist of IPv4 and IPv6 addresses and ranges, with a button to add your own address, and the addresses locked out now, with an Unlock button.
  • The same error for a wrong username and a wrong password.
  • An optional logout after a time without activity. An open dashboard tab does not keep the login alive.

Two-factor authentication

  • A TOTP code (RFC 6238) from an authenticator app such as Google Authenticator, Microsoft Authenticator, Aegis or 2FAS.
  • Each user sets it up under Users > Two-factor with a QR code drawn by the plugin itself, so the key never reaches an outside service.
  • Ten single-use backup codes, stored as hashes; the app key is stored encrypted.
  • Required for chosen roles: those users set up their app at their next login.
  • The password alone never starts a session, and wrong codes count toward the lockout. XML-RPC programs use an application password.
  • Trusted browsers skip the code for the days you choose (30 by default, 0 to always ask); each user can forget them all.
  • Administrators can turn it off for a user who lost both the phone and the backup codes.

Firewall

  • Checks every request before other plugins load, from a small must-use plugin that Rocca writes and removes with the switch.
  • Rules, each with its own switch: SQL injection, script injection, path traversal and file inclusion; probes for .env, .git, backups and database dumps; known vulnerability scanners; methods WordPress does not use.
  • Only the address, method, address bar and user agent are checked, never form data.
  • Block mode, or log-only mode to try the rules first. Blocked addresses and ranges, and an optional limit of requests per minute.
  • Repeat offenders, and visitors who ask for many missing pages as scanners do, are blocked for a while, with an Unblock button. Each log line has a Block button.
  • A log of the latest matches; a blocked visitor sees a reference you can find there.
  • An emergency switch in wp-config.php. The rules ship with the plugin: no outside rule feed.

Activity log

  • Logins, logouts, lockouts, password resets, two-factor and application password changes.
  • Users created, deleted, given another role, or with a new email address or password. Passwords are never stored.
  • Plugins, themes and WordPress installed, updated, activated, deactivated, switched or deleted.
  • Important settings, such as the site address and the admin email, with the value before and after.
  • Filters, pages and CSV download. Written with one query per request, deleted after 90 days by default.

File checks

  • Every day, a background check fingerprints the PHP, JavaScript, .htaccess and .user.ini files of WordPress, plugins, themes, must-use plugins and uploads.
  • The first check becomes the baseline. Later checks list changed, new and missing files to accept; PHP in uploads is always listed.
  • Updates made from the dashboard refresh the baseline, so a normal update raises no alarm.
  • An email to the site administrator when a check finds something new. Rocca never changes or deletes a file.

Hardening

  • Turns off the file editors, limits or turns off XML-RPC, hides usernames from visitors and removes the WordPress version.
  • Sends X-Content-Type-Options, X-Frame-Options and Referrer-Policy on public pages, unless already set.
  • Stops PHP files in the uploads folder from running: a marked .htaccess rule on Apache and LiteSpeed, and the rule to copy for nginx.

Reports and tools

  • A weekly summary email to the site administrator, on by default.
  • Checks in Tools > Site Health: firewall, two-factor for administrators, files, PHP in uploads, visitor address.
  • WP-CLI: wp rocca status, unlock, firewall on|off|status, scan, 2fa reset and report.

Behind a proxy

By default Rocca uses the address of the direct connection. Behind Cloudflare or another proxy, choose its header on the Settings page, which shows the value of each header for your own request.

Privacy

Rocca stores what it needs in your own database, and each kind of record is deleted after a period you choose:

  • A failed login: the IP address, the name typed and the time. 30 days by default.
  • A request stopped or logged by the firewall: the IP address, method, address requested, user agent and time. 30 days by default.
  • The activity log: the username, IP address and time of each action. 90 days by default. An erasure request removes the person’s username and address from their entries and keeps the events.
  • Two-factor: an encrypted app key, hashes of the backup codes and of trusted browser tokens, stored with the user’s account until two-factor is turned off.

Rocca adds a suggested paragraph to the privacy policy guide and supports the WordPress personal data export and erase tools.

DROVNE Rocca is an independent plugin. It is not affiliated with or endorsed by WordPress or Automattic.

Screenshots

The overview: what each module does now, and the figures of the last 24 hours.
The overview: what each module does now, and the figures of the last 24 hours.
Login protection: the attempt limit, the allowlist and the addresses locked out now.
Login protection: the attempt limit, the allowlist and the addresses locked out now.
Two-factor setup: scan the QR code, drawn by the plugin itself, or type the key.
Two-factor setup: scan the QR code, drawn by the plugin itself, or type the key.
The firewall: rules, log-only mode and the latest matches with their reference.
The firewall: rules, log-only mode and the latest matches with their reference.
The activity log, filtered by kind of action, with the values before and after.
The activity log, filtered by kind of action, with the values before and after.
File checks: code in uploads and changed files, to accept or look at.
File checks: code in uploads and changed files, to accept or look at.

Installation

  1. Install and activate the plugin. Login protection, hardening, the activity log and the daily file check start right away; the first file check makes the baseline.
  2. Open Rocca in the admin menu and check the Overview.
  3. If the Overview warns that your address is private, choose your proxy header on the Settings page before anything else.
  4. Set up two-factor for your own account under Users > Two-factor, then choose on Rocca > Two-factor which roles must use it.
  5. Turn on the firewall on Rocca > Firewall. On a busy site, start with “Only log it” for a few days and look at the matches.

FAQ

I locked myself out. What now?

Wait until the lockout ends, or log in from another network and press Unlock on the Login protection page. With WP-CLI, run wp rocca unlock followed by your address. If you cannot wait, rename the plugin folder over FTP or your host’s file manager: WordPress then deactivates it.

I lost my phone. How do I log in?

Enter one of your backup codes instead of the app code, then set up your new phone under Users > Two-factor. Without backup codes, ask an administrator to turn two-factor off on your profile. If you are the only administrator, rename the plugin folder over FTP or your host’s file manager to deactivate it, log in, and rename it back.

What happens if I change the security keys in wp-config.php?

The app keys are encrypted with a key made from them, so they can no longer be read: users log in with a backup code and set up their app again. To keep the app keys across a change, define DROVNE_RC_SECRET_KEY in wp-config.php with a long random value before users set up their apps.

A firewall rule blocks something my site needs. What now?

Switch the firewall to log-only mode, or turn off that rule on the Firewall page. If you cannot reach the dashboard, add define( ‘DROVNE_RC_FIREWALL_OFF’, true ); to wp-config.php, fix the setting, then remove the line. Addresses on the allowlist are never stopped.

Does the firewall replace a server firewall or a hosted firewall?

No. It sees only requests that reach WordPress, after the web server. Static files and pages served from a page cache never reach it.

Why not compare WordPress files with the official checksums?

Those come from WordPress.org, and Rocca contacts no outside server. The local baseline also covers premium plugins and your own code, which have no public checksums. If the site was already infected before the first check, the baseline includes the infection: start on a clean copy, or look at the files the first check lists in uploads.

Does Rocca send data anywhere?

No. Everything is stored in your own database. The only messages that leave the site are the file check email and the weekly summary, sent by your own site to its administration email address, and you can turn each off.

Will it slow my site down?

Public pages get a few filters and, with the firewall on, a handful of pattern checks on the address. The database is read on login requests, written when the firewall stops a request, and once per request only if you set a rate limit without a persistent object cache.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“DROVNE Rocca” is open source software. The following people have contributed to this plugin.

Contributors
  • DROVNE

Translate “DROVNE Rocca” into your language.

Interested in development?

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

Changelog

0.2.0

  • Automatic blocks of repeat offenders and scanners, Block and Unblock buttons, no PHP in uploads, trusted browsers, logout after inactivity, weekly summary, Site Health checks and WP-CLI commands.

0.1.0

  • First version: login attempt limits with growing lockouts, allowlist, generic login errors, two-factor authentication with backup codes and required roles, a firewall that starts before other plugins, an activity log, daily file checks against a local baseline, hardening switches and security headers.

Meta

  • Version 0.2.0
  • Last updated 13 hours ago
  • Active installations Fewer than 10
  • WordPress version 7.0 or higher
  • Tested up to 7.1.5
  • PHP version 8.1 or higher
  • Tags
    Brute Forcefirewallloginsecuritytwo factor
  • Advanced View

Ratings

No reviews have been submitted yet.

Your review

See all reviews

Contributors

  • DROVNE

Support

Got something to say? Need help?

View support forum

  • About
  • News
  • Hosting
  • Privacy
  • Showcase
  • Themes
  • Plugins
  • Patterns
  • Learn
  • Documentation
  • Developers
  • WordPress.tv ↗
  • Get Involved
  • Events
  • Donate ↗
  • Swag ↗
  • WordPress.com ↗
  • Matt ↗
  • bbPress ↗
  • BuddyPress ↗
WordPress.org

The WordPress® trademark is the intellectual property of the WordPress Foundation.

  • Visit our X (formerly Twitter) account
  • Visit our Bluesky account
  • Visit our Mastodon account
  • Visit our Threads account
  • Visit our Facebook page
  • Visit our Instagram account
  • Visit our LinkedIn account
  • Visit our TikTok account
  • Visit our YouTube channel
  • Visit our Tumblr account
Code is Poetry