How-Tos

How-To: Audit and Revoke the WordPress Application Passwords Your Bots Use

Leave a comment

My blog bots talk to WordPress over the REST API with Application Passwords, never my real login. That’s the right pattern, but those passwords pile up. Here’s how I keep them tidy with WP-CLI. Run this on the server as a user who can run WP-CLI against your site.

1. List them, with last-used info

wp user application-password list YOUR_USER --fields=uuid,name,created,last_used,last_ip

Every bot should have its own clearly named password (“research-bot”, “drafts-bot”). Anything you don’t recognize, or that hasn’t been used in months, is a candidate to remove.

2. Revoke the ones you don’t need

wp user application-password delete YOUR_USER UUID_HERE

If a bot’s machine or config ever leaks, revoke its password first and ask questions later. Your real password and the other bots keep working.

3. Create a fresh one per bot

wp user application-password create YOUR_USER "drafts-bot" --porcelain

--porcelain prints only the new password. Store it in that bot’s secret store or a locked-down env file (mode 600), never in Git.

4. Use the least-privileged account you can

An Application Password has the same capabilities as the user it belongs to. If a bot only writes drafts, give it its own Author or Contributor account instead of an admin one.

Put a reminder on your calendar to run step 1 monthly. It takes 30 seconds.

God Bless, and Use the Source!

References & Further Reading

Subscribe (RSS) Follow How-Tos via RSS

Leave a note

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.