LifterLMS Security Checklist: Hardening Your Course Site

A practical LifterLMS security checklist covering updates, captcha and spam protection at checkout, roles, payment gateways, API keys, protected files, accounts, personal data and backups, with the exact settings to check.

  • Add as a preferred source on Google
Illustration for “LifterLMS Security Checklist: Hardening Your Course Site”

A course site is a more attractive target than a brochure site. It stores customer names, addresses and order history, takes payments, and holds paid content that people would rather not pay for. LifterLMS security is mostly WordPress security, plus a handful of LMS-specific settings that are easy to miss.

This checklist is for site owners and the people who maintain LifterLMS sites. Work through it once, then revisit it every quarter. Every LifterLMS setting named here was checked in the 10.3 plugin source; general WordPress hardening is covered in the official Hardening WordPress handbook, which is worth reading alongside it.

The checklist at a glance

AreaCheck
UpdatesLifterLMS, add-ons, WordPress, theme and PHP current; updates tested on staging
Checkout and formsCaptcha on, Spam Protection on, Akismet if available
LoginsStrong passwords, two-factor for staff, login rate limiting, concurrent logins limited
RolesFew administrators, LMS Manager and Instructor roles used deliberately, preview access reviewed
PaymentsOfficial gateway add-ons, HTTPS everywhere, test mode off production only
API and webhooksOne key per integration, least permission, unused keys revoked, signatures verified
Files and contentDownloadable files protected, server rules tested
DataLogs cleared, exports deleted, privacy tools working
BackupsAutomatic, off-site, restore tested

1. Keep LifterLMS and everything around it updated

LifterLMS ships security fixes regularly. The 10.x changelog alone includes additional authorization checks on REST API endpoints, hardened course import handling, stricter redirect handling, and template loading checks in 10.3.2. Running an old version means running with known, published issues.

  • Update LifterLMS core and every LifterLMS add-on together, so versions stay compatible.
  • Keep WordPress, your theme and PHP on supported versions.
  • Test updates on a staging copy first, especially on sites with custom code. Our guide to working on a LifterLMS staging site explains how to do that without charging subscribers twice.
  • Remove plugins and themes you no longer use. Deactivated code can still be attacked.

If you maintain template overrides in your theme, review them after major updates. An outdated override can miss fixes made to the original template.

2. Protect checkout and registration from bots

Card-testing bots love checkout forms, and spam registrations fill your student list with junk. LifterLMS has three defences under LifterLMS > Settings > Security, in the Website Security & Spam Prevention section.

Captcha

Set Captcha to reCAPTCHA or Turnstile. It is added to the checkout form, the registration form and the free enrollment form.

  • For reCAPTCHA, enter the reCAPTCHA v3 Site Key and reCAPTCHA v3 Secret Key, and set the reCAPTCHA Minimum Score on a 1 to 10 scale; the setting notes that Google recommends 5.
  • For Cloudflare Turnstile, enter the Turnstile Site Key and Turnstile Secret Key. The Turnstile setup guide walks through getting the keys and testing.

Since 10.3.1, saved secret keys are partially hidden on the settings screen. To replace one, enter the new key; to remove it, clear the field.

Spam Protection

Keep Spam Protection ticked. It blocks an IP address from checkout when there are more than 10 failures within 15 minutes, which stops most card-testing runs. It is on by default; make sure nobody has switched it off while debugging.

Akismet

If the Akismet plugin is active and connected, an Akismet Spam Protection option appears in the same section. Enable it for an extra spam check on submissions.

What these do not cover

The LifterLMS captcha protects LifterLMS checkout and registration forms. It does not protect the WordPress login page or the LifterLMS login form against password guessing. Add login rate limiting through your host, a firewall or a reputable security plugin. If you do not need public sign-ups, leave Open Registration off under LifterLMS > Settings > Accounts.

3. Lock down logins and roles

  • Two-factor authentication for every administrator and LMS Manager. Course site admins can issue refunds, change prices and export student data.
  • As few administrators as possible. Give course staff the LifterLMS roles instead: LMS Manager for people who run the LMS, Instructor for people who create and teach courses, and Instructor's Assistant for helpers.
  • Review Unrestricted Preview Access under LifterLMS > Settings > General. Roles listed there bypass enrollment, drip and prerequisite restrictions. By default that is administrators, LMS Managers, instructors and assistants; remove any role that should not see all content.
  • Remove staff accounts the day someone leaves, and reassign their courses.
  • Limit account sharing with Prevent concurrent logins, explained in our guide to stopping account sharing.

Also disable the built-in theme and plugin file editors on production by adding this line to wp-config.php. It is a WordPress core constant, and it means a stolen admin password cannot be used to edit PHP from the dashboard:

define( 'DISALLOW_FILE_EDIT', true );

4. Payments and gateways

  • HTTPS on every page, not only checkout. Login cookies travel on every request.
  • Use the official gateway add-ons for Stripe, PayPal and other providers, and keep them updated with core. Never collect card numbers in a custom form field.
  • Keep live keys on production only. Staging and development copies should run gateways in test mode. Each gateway add-on has its own test mode setting.
  • Restrict who can refund. Order management, refunds and the Customers screen are available to administrators and LMS Managers.
  • Watch for card testing. A burst of small failed payments in your gateway dashboard means bots have found the checkout. Check that captcha and Spam Protection are on.

5. REST API keys and webhooks

API keys live under LifterLMS > Settings > REST API. Each key acts as a WordPress user, with Read, Write or Read / Write permission.

  • One key per integration, tied to a dedicated user with the lowest role that works, so you can revoke one without breaking the rest.
  • Read-only keys for anything that only reports.
  • Revoke keys you no longer use. The screen shows when each key was last accessed.
  • Verify the signature on every webhook your systems receive, and use a strong secret.
  • Turn webhook delivery logging off once debugging is done, because logs can contain student data.

The details are in our introduction to the LifterLMS REST API and webhooks.

6. Files and content

  • Protect downloadable course files by assigning them to a course or membership, so their URLs only work for enrolled students. See how to protect course files in LifterLMS.
  • On Nginx, add a server rule that blocks direct access to wp-content/uploads/lifterlms/. The automatic .htaccess rule only works on Apache-compatible servers.
  • Test from a private window. Try a protected file's direct path while logged out.
  • Use Content Protection under General settings if casual copying is a concern, knowing it is a deterrent and not real protection.
  • Use video host privacy settings, such as domain-restricted embeds, for hosted video.

7. Personal data and privacy

A LifterLMS site holds names, emails, billing addresses, order history, quiz answers and progress. Treat it accordingly.

  • LifterLMS adds its data to the WordPress personal data export and erasure tools under Tools. Test both with a dummy account so you know they work when a request arrives.
  • Clear old files under LifterLMS > Status > Logs and delete CSV exports from your computer after use.
  • Limit who can export reports. Instructors can see data for their own courses; decide whether that is appropriate.
  • Keep a record of which third-party services receive student data: email platforms, CRMs, analytics.

8. Backups, monitoring and recovery

  • Automatic daily backups of files and the database, stored off the server. Busy sites with many orders need more frequent database backups.
  • Test a restore to staging at least twice a year. A backup you have never restored is a hope, not a plan.
  • Uptime and change monitoring. Get alerted when the site goes down or files change unexpectedly.
  • Check scheduled tasks. Recurring payments, emails and webhooks run through the scheduler under LifterLMS > Status > Scheduled Actions. A pile of failed or past-due actions can be the first sign something is wrong.
  • Have an incident plan: who to call, how to put the site in maintenance mode, how to rotate passwords and API keys, and how you will tell affected students.

Common mistakes

  • Turning off Spam Protection to fix a checkout problem and never turning it back on.
  • Sharing one admin login between staff members instead of giving each person a role.
  • Live gateway keys on a staging clone.
  • API keys tied to a personal admin account that disappears when the person leaves.
  • Trusting .htaccess on Nginx.
  • Backups stored on the same server as the site.

Frequently asked questions

Is LifterLMS secure?

LifterLMS is actively maintained and ships security fixes regularly, with credited researchers in its changelog. As with any WordPress plugin, your site's security depends on keeping it updated and configuring the rest of the site well.

Does the LifterLMS captcha protect the login page?

No. It covers checkout, registration and free enrollment forms. Protect logins with rate limiting and two-factor authentication.

Do I need a security plugin as well?

Usually yes, or an equivalent firewall from your host. LifterLMS handles LMS-specific risks; login protection, malware scanning and a web application firewall come from elsewhere.

How often should I review this checklist?

Quarterly, and after any major change such as a new integration, a new staff member, a host move or a large update.

What to do next

Start with the three changes that block the most real attacks: captcha and Spam Protection on checkout, two-factor for every staff account, and current versions of everything. Then work down the table above.

If you would rather have someone else own this, our LifterLMS support plans cover updates, monitoring and security reviews, including server configuration such as protected file rules. Ask us for a security review of your course site.

Add LifterLMS Expert to your preferred sources

Add lifterlmsexpert.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.

  • Add as a preferred source on Google
Free consultation

Prefer expert help over DIY?

Skip the trial and error. Get specialist LifterLMS help and ship faster.

Talk to a LifterLMS Expert Explore our services

Replies within one business day