Description
SiteAgent turns every WordPress site into one an AI agent can safely operate — update, maintain, audit, and fix. Once the site is connected to Aura and its approval key is provisioned, mutating actions are gated behind human approval and recorded in a full audit trail; safe batch updates and block edits are snapshotted so they can be rolled back. It’s the on-site half of Aura, the governed control room agencies use to run whole fleets of client sites alongside their servers, CDN, and DNS.
Plugin and core updates are the riskiest thing you do on a live client site. SiteAgent makes them safer: safe batch updates run behind health checks and roll back automatically if the site breaks, and every plugin in that path is zip-snapshotted first. With Aura’s approval key in place, an agent can’t silently push a change — mutating actions wait for a human to approve them. Think of it as the undo button for AI on your clients’ sites.
Install this plugin on any WordPress site to connect it to Aura — no SSH, no wp-admin juggling, no manual logins.
What You Can Do
- Monitor site health — See WordPress version, PHP version, installed plugins & themes, database info, and disk usage in real time.
- Update plugins, themes & core remotely — Push updates to any connected site from the Aura dashboard, no wp-admin login.
- Safe batch updates with auto-rollback — Run chunked updates with health checks; if an update breaks the site, the plugin restores the previous version automatically.
- Per-plugin rollback — Every update is zip-snapshotted first; restore any plugin to its last good state on demand.
- Bulk translation & database upgrades — Update all language packs and run WordPress database migrations remotely.
- One-click connect (magic link) — Connect a site to Aura straight from wp-admin — no manual token copy/paste.
- AI-agent ready (27 MCP tools) — Exposes machine-readable, JSON-schema tools for AI-driven management, including SEO/accessibility/performance/broken-link auditors, on-site SEO-meta read/write (Rank Math, Yoast, SEOPress), and Gutenberg block read/edit. Read tools run on demand; mutating tools are approval-gated through Aura, and every call is audited.
- Zero frontend impact — The plugin only registers REST API endpoints. No scripts, no styles, no database queries on visitor-facing page loads.
How It Works
After activation, click Connect to Aura on the Settings → SiteAgent page for a one-click magic-link connection, or copy the Site Token shown once and paste it into your Aura dashboard manually. From that point, Aura communicates with your site over a signed, authenticated REST API to pull health data and push updates.
Security
Defence-in-depth protects every request:
- WordPress Application Password — Standard WordPress auth with capability checks (
manage_options/update_*). Only authorized administrators can trigger actions. - Hashed Site Token — A per-site token sent via the
X-Aura-Tokenheader. Only a SHA-256 hash is stored (never the raw token), compared timing-safely. Tokens from older versions migrate to a hash automatically. - Brute-force throttling — Repeated bad-token attempts from an IP are blocked.
- Signed magic-link connect — The onboarding callback is HMAC-signed with a one-time secret and timestamp, so the token exchange can’t be hijacked or replayed.
- IP / Domain allowlist (optional) — Restrict API access to your Aura instance, with Cloudflare and reverse-proxy header support.
You can rotate the token anytime from Settings → SiteAgent → Regenerate Token.
REST API Endpoints
Core endpoints under /wp-json/aura/v1/:
GET /status— Full site health reportGET /updates— Check available updates (core, plugins, themes, translations)POST /update/core//update/plugin//update/theme//update/translations— Apply updatesPOST /update/database— Run WordPress database upgradesPOST /connect— Magic-link token exchange (public, HMAC-signed, 10-minute expiry)
Version 2 endpoints under /wp-json/aura/v2/:
GET /health— HTTP, PHP fatal, white-screen and DB connectivity checksPOST /update/batch— Chunked batch updates with auto-rollback on health failurePOST /rollback/{plugin}— Restore a plugin from its most recent backupPOST /rules— Receive Aura’s signed operator ruleset; carryingunbind: trueit ends this site’s binding instead
While a site is disconnected by Aura, every write endpoint answers
403 aura_site_unbound and reads keep working; the disconnect answer carries
cleanup_complete and leftovers (what the site still holds), and GET /status
reports unbound until the site is reconnected or the remaining Aura data is removed
from the settings screen.
MCP tools under /wp-json/aura/mcp/:
POST /tools/list/POST /tools/execute— Enumerate and run AI-agent toolsGET /context— Full site context for AI decision-making
AI Agent Tools (MCP)
SiteAgent ships 29 built-in tools for AI agents. Read tools return information and run on demand; write tools change the site and are queued for human approval through Aura — an agent can never silently mutate a production site.
Read tools:
get_site_context— WordPress/PHP/theme/plugin/disk/performance snapshot with detected issuesget_database_info— Database size, largest tables, autoloaded-options weight, expired transientsscan_security— Scored security posture (file-edit lockdown, debug exposure, SSL, default admin/prefix, open registration, PHP version)scan_seo— SEO posture (search-engine visibility, permalinks, XML sitemap, site title) plus a sampled content audit (thin content, missing excerpts/featured images)scan_a11y— Accessibility audit over sampled content (images missing alt text, non-descriptive link text, heading structure, document language)perf_check— Performance posture (persistent object cache, OPcache, page-cache plugin, PHP version, autoload weight, active plugin count, memory limit)scan_broken_links— Link triage over a content sample with no outbound HTTP (empty/anchor-only links, dev/staging hosts, unresolved internal links)list_users— Users with roles and post counts, administrators flagged (never returns secrets)check_health— Live health gate: HTTP status, PHP fatals, white-screen, database connectivityscan_error_log— Tails and severity-groups the error log, surfacing recent fatalscheck_vulnerabilities— Plugin update-currency check against WordPress.org (a version check, not a vulnerability/CVE feed; covers wp.org-hosted plugins)check_core_checksums— Core-file integrity against the official WordPress.org checksum manifest (modified/missing/unexpected files, fetched over HTTPS only)scan_executable_files— Uploads-directory observations: PHP/executable files, .htaccess overrides, and symlinks (reported, never followed)audit_admin_accounts— Privileged-account facts: administrators with recency, admin capabilities outside the role, application-password counts, multisite super adminsaudit_cron— Bounded WP-Cron inventory with sub-60-second-schedule and unresolved-callback fact-flagsaudit_public_backups— Full-site backups and database dumps left inside the webroot, and whether the site serves themaudit_mcp_exposure— Which other MCP servers are registered on this site, and how many abilities pass the discovery rule such a server applies (abilities are registered site-wide, not per-plugin, so a server resolving targets from that registry picks up mutating ones outside SiteAgent’s approval path). The counts describe the abilities, not what any server currently serves. Reports only; changes nothingaudit_agent_code— Executable code an AI agent authored or can author on this site: Angie code snippets (recorded, agent-authored, live per environment), the SiteAgent Power Pack’s execute-php / file-write / wp-cli flags, and third-party exec stores. Counts and presence only; never file contents, never a verdict. Reports only; changes nothingaudit_rules— Whether a signed operator ruleset is present and how old it is, 24h block/warn counts, expired-but-listed rules, and the enforcement points in this build. Reports only; changes nothingget_seo_meta— Read a post/page’s SEO title, description, and focus keyword from the active SEO plugin (Rank Math, Yoast, or SEOPress)list_page_blocks— Read a page’s Gutenberg block structure (block names, attributes, nesting)snapshot_get— Retrieve a stored snapshot of page content (reversible write metadata)
Write tools (approval-gated):
elementor_replay_ability— Executes an approved held Elementor write (destructive, requires Aura approval): claims the hold, re-judges it against the current ruleset, and runs the original Elementor mutation as the user who askedupdate_plugin_safely— Backup, update, health-check, auto-rollback on failureclear_caches— Flush object/opcode caches and detected page-cache pluginscleanup_transients— Remove expired transients to reduce autoload bloatcleanup_orphaned_assets— Find and remove unused media (dry-run by default)backup_plugins— Zip-snapshot one or all active plugins as a rollback safety netset_seo_meta— Write a post/page’s SEO title / description / focus keyword on the active SEO plugin (Rank Math, Yoast, or SEOPress) — on-site, so it works even when a WAF blocks the plugin’s own REST endpointupdate_page_block— Update a Gutenberg block’s content or attributes (snapshot-first, reversible)create_page_from_blocks— Create a new page from a Gutenberg block spec (draft-first)
Tools are classified by verb so the Aura Fleet gateway applies the right risk and approval policy automatically.
Pro: the SiteAgent Power Pack
Everything above is free and ships in this plugin. Agencies that need an agent to fix a site — not just report on it — can add the SiteAgent Power Pack, a separate companion plugin that registers higher-capability tools through this plugin’s own tool registry.
It is not included in this download and is not distributed on WordPress.org — the tools it adds execute code, so they don’t belong in a hosted repository. It comes with the Aura Agency and Studio plans, or as SiteAgent Pro.
What it adds:
read_file— read a text file from inside wp-content (jailed; refuses wp-config.php).db_query— a single read-only SQL statement (SELECT / SHOW / EXPLAIN), row-capped.write_file— write a file inside wp-content, snapshot-first so it can be rolled back.run_wp_cli— run an allowlisted WP-CLI command, with no shell and no metacharacters.execute_php— run a PHP snippet against the full WordPress API.
These are governed harder than anything in the free set, deliberately:
- Off until you arm them. The write and code tools do nothing until the site owner sets an explicit constant in
wp-config.phpfor each one. Installing the Power Pack alone enables no writes and no code execution. - Human approval, cryptographically enforced. Once the site holds Aura’s approval key (provisioned when you connect the site), each of these calls requires a single-use, signed grant bound to that exact tool and its exact parameters — one only the Aura dashboard can mint, after a human approves the action. A leaked Site Token cannot run them. (Until a site has that key, the gate is dormant — so connect the site from Aura before arming anything.)
- Reversible where it can be. File writes are snapshotted first, so there’s a previous state to restore.
The safety model is governance, not a sandbox: execute_php is powerful by design. The controls are the constant you set, the human who approves the call, and the audit trail — not a promise that arbitrary code is safe.
Learn more at my-aura.app/siteagent.
About Aura
Aura is a full-stack operations dashboard by Digitizer that brings servers, applications, DNS zones, and CDN pull zones from Cloudways, Hostinger VPS, Cloudflare, and Bunny.net into a single unified interface.
SiteAgent extends that reach into every WordPress installation — so you can manage your entire infrastructure, including WordPress sites, from one place.
Free to Use
The plugin is completely free and open source (GPLv2+). You need a free or paid Aura account to connect your sites. Sign up at my-aura.app.
Links
Installation
Via WordPress Admin (Recommended)
- Go to Plugins → Add New in your WordPress admin.
- Search for SiteAgent.
- Click Install Now, then Activate.
- Navigate to Settings → SiteAgent.
- Click Connect to Aura for one-click magic-link onboarding — or copy the Site Token (shown once) and paste it into your Aura dashboard manually.
Via WP-CLI
wp plugin install digitizer-site-worker --activate
Manual Upload
- Download the plugin ZIP from WordPress.org.
- Go to Plugins → Add New → Upload Plugin.
- Upload the ZIP and click Install Now, then Activate.
- Navigate to Settings → SiteAgent to connect or get your Site Token.
FAQ
Do I need an Aura account?
Yes, you need an Aura account to connect your WordPress sites. Aura offers a free tier that includes up to 3 WordPress sites. Sign up at my-aura.app.
Is this plugin safe to use?
Yes. The plugin uses defence-in-depth: WordPress Application Passwords (the same standard mechanism used by the block editor), a per-site token stored only as a SHA-256 hash and verified timing-safely, per-IP brute-force throttling, an HMAC-signed onboarding handshake, and an optional IP/domain allowlist. No data is transmitted unless a request is made by your Aura instance.
How do I enable the approval gate for write actions?
SiteAgent can require a per-action, cryptographically signed approval before it runs a state-changing MCP tool (cleanups, cache flushes, SEO writes, safe plugin updates run through the tool interface). Once enabled, each such write must carry a single-use signature that only the Aura dashboard can mint, after a human approves the action — so a leaked Site Token cannot run those tools on its own.
This gate turns on automatically once the site holds Aura’s approval key, which is provisioned securely during connection. If you installed or updated the plugin but have not reconnected the site since, the gate is dormant and the site runs in the standard token-only mode. To activate it, simply reconnect the site from your Aura dashboard — no reinstall is needed.
Note: the approval gate currently covers the MCP tool path. Core, plugin, and theme updates performed over the plugin’s direct REST update endpoints are still authorized by the Site Token alone (the standard site-management model), so treat the Site Token as a sensitive credential regardless. Grant coverage for those update endpoints is on the roadmap.
Does it slow down my site?
No. The plugin registers only REST API endpoints. It does not load any code, scripts, or database queries on frontend page loads. Your visitors experience zero impact.
What WordPress versions are supported?
WordPress 6.2 or higher is required. This is needed for full Application Password support. The plugin has been tested up to WordPress 7.1.
What PHP versions are supported?
PHP 7.4 or higher. PHP 8.0+ is recommended.
Can I restrict which IP addresses can access the API?
Yes. The plugin supports an optional IP whitelist. If configured, only requests from the specified IP addresses will be accepted. Cloudflare and reverse proxy headers (CF-Connecting-IP, X-Forwarded-For, X-Real-IP) are fully supported for IP detection.
Does this work with WordPress multisite?
The plugin is designed for single WordPress installations. Multisite support is not currently available but is on the roadmap.
Where is the Site Token stored?
Only a SHA-256 hash of the Site Token is stored, in the WordPress option aura_worker_site_token — the raw token is never persisted. It is generated on first activation and shown once so you can copy it; the Aura dashboard keeps the only raw copy. Tokens created by older versions are upgraded to a hash automatically on first use.
Can I regenerate the Site Token?
Yes. Use Regenerate Token on the Settings → SiteAgent page. The new token is shown once. Regenerating invalidates the old token and disconnects the site from Aura until you reconnect with the new one.
How do I disconnect a site from Aura?
Remove the site from your Aura dashboard, or deactivate or delete the plugin. If you deactivate the plugin, the REST API endpoints are unregistered and Aura can no longer communicate with the site.
Since 2.13.0, disconnecting from the Aura dashboard happens in two phases. The site is marked disconnected immediately and refuses every change from that moment on — reads keep working — and Aura then has it revoke the Application Password it minted, clear the stored ruleset and gateway key, and finally delete the site token. If the site was mid-disconnect when it lost contact, it finishes the job by itself on its next page load.
Aura disconnected my site but something is left behind — what do I do?
Open Settings → SiteAgent. A disconnected site says so (“Disconnected by Aura at …”) and offers Remove remaining Aura data, which revokes what is left and clears the disconnect record — but only once everything it names, the site token included, is proven gone. If it tells you it cannot say which user holds an Application Password, revoke it under Users → Profile → Application Passwords and try again. Reconnecting the site to Aura also clears the record, after settling what the previous connection still owed.
Does Aura store my wp-admin credentials?
No. Aura uses WordPress Application Passwords, not your main admin password. Application Passwords are scoped specifically for REST API access and can be revoked at any time from Users → Your Profile in wp-admin.
Is the plugin open source?
Yes. SiteAgent is open source under the GPLv2 or later license. The source code is available on GitHub.
Screenshots







Changelog
2.26.0
- New: that proof is now also sent when the connection link is created, so Aura recognizes a moved site before it checks the plan’s site limit. An organization at its limit can reconnect a site that moved to a new domain.
2.25.0
- New: a site that reconnects to Aura after moving to a new domain now proves it held its previous connection, so Aura can keep the same site record (its history and settings) instead of creating a second one. The proof is a one-way signature; no token or token hash is sent.
2.24.4
- Elementor 4.4.0: five of its new read tools (find-icons, get-license-status, get-system-info, list-experiments, and get-widget-schemas, the new name of get-widget-schema) are no longer refused by SiteAgent’s Elementor governor. Each was checked to change nothing. Elementor 4.4.0’s new write tools stay refused until they are reviewed, and so do its Pro-discovery tools, because Elementor Pro registers real tools under the same names.
2.24.3
- Fix: the MCP exposure audit failed on sites running MCP adapter 0.7 (bundled with Elementor 4.4.0). Its server list, Angie and MCP-module sections returned an error instead of their findings. The audit now counts each server’s tools under the adapter’s newest schema, and reports an unreadable server as unknown instead of failing.
2.24.2
- Security: when PHP cannot create the private backup folder (wp-content/aura-backups/ owned by another user), a backup is now refused with a clear error instead of being saved where it can be downloaded. Old backups that could not be moved are retried, and site context reports them.
2.24.1
- Security: plugin backups taken before an update are now stored in a folder with an unguessable name. They used to sit in wp-content/aura-backups/, protected only by an .htaccess rule that nginx ignores, so on nginx hosts anyone who knew a file’s name could download it. Existing backups move to the new folder on upgrade.
- Only the three newest backups per plugin are kept; older ones are deleted after each backup, never one less than 30 minutes old, which an update in progress may still need.
- The public-backup check now looks in SiteAgent’s own backup folder too.
2.24.0
- New: a security check for full-site backups and database dumps left where the web server can serve them (All-in-One WP Migration, UpdraftPlus, Duplicator, .sql files and archives). It reports each file’s name, size and date, and whether the site actually serves it, without reading any contents. Found on three sites during a fleet update round.
2.23.9
- Fix: when a host does not let SiteAgent write plugin files, the refusal now says which step of the check failed. Before, the step was recorded on the site but left out of the answer, so finding it took shell access.
2.23.8
- Fix: the site report no longer says plugins are up to date when WordPress’s list of available updates is old. On a site where scheduled tasks do not run, that list could be days old, and the report showed 0 updates on sites many versions behind. The list is now checked again when it is more than 12 hours old, the report says when it was last checked, and it says so when WordPress.org could not be reached.
2.23.7
- New: after Aura updates Elementor, Elementor Pro, WooCommerce or JetEngine, SiteAgent says whether the plugin’s database upgrade is still due, and Aura can run it. Before, the database was upgraded only the next time someone opened wp-admin.
2.23.6
- Fix: plugin updates requested at the same time no longer run side by side. WordPress clears its shared upgrade folder before each update, so updates that overlapped broke each other (“Could not copy file”). SiteAgent now runs one plugin update at a time; another one requested meanwhile is refused as busy, changes nothing, and can be retried.
- Fix: a plugin is updated only when the name given matches it exactly. A partial name could pick a different plugin.
2.23.5
- Fix: updating Crocoblock plugins through Aura now works on real sites. 2.23.3 registered the plugin with Crocoblock’s dashboard but could skip building its update checker, so still no update was offered.
- A refused plugin update now says whether SiteAgent registered the plugin’s own updater.
2.23.4
- When SiteAgent refuses to update plugins because the host seems to block PHP file writes, it now records which step failed (writing or deleting, a test file or a PHP file), so a mistaken refusal can be diagnosed from Aura without shell access.
2.23.3
- Fix: Crocoblock plugins (JetEngine, JetSmartFilters and the other Jet plugins) can now be updated through Aura. Their updater registers only inside wp-admin, so an update requested by Aura found no update on offer even with an active licence. SiteAgent now registers it first, the way wp-admin does.
- When no update is on offer, the answer now names the installed version.
2.23.2
- Security: when SiteAgent cannot confirm it governs Elementor’s AI writes on a site, those writes are now refused on every connection, not only on Elementor’s own two. Other plugins’ MCP servers (Atarim 5.1.8, for one, which serves every installed plugin’s abilities) run the same Elementor code, and could reach it while those two were closed. Reads, the Elementor editor and sites where coverage is confirmed are unaffected.
2.23.1
- Fix: updating a plugin through Aura no longer leaves it deactivated. WordPress switches a plugin off while it updates it, and only its own admin screen switches it back on; SiteAgent now turns an active plugin back on after the update, whether the update worked or failed. An inactive plugin stays inactive.
- SiteAgent no longer updates itself through the generic plugin update, which could switch it off and cut Aura off from the site. It updates itself only through its own protected self-update.
- A failed update now reports WordPress’s actual reason instead of “No update available”, and an update that is not on offer is reported as such rather than as an error. The update list is refreshed once before updating when the plugin is missing from it.
2.23.0
- Operator rules about custom CSS now also cover Elementor’s publish-document when publishing would take a pending autosave live, since that autosave can carry CSS no rule has seen. A publish with no autosave is unaffected. If an autosave appears while a call is being approved or run, the call is stopped and can be retried, or it publishes without that autosave, which stays waiting for the next publish. No new settings.
2.22.0
- New: an install ledger. Every plugin and theme install or update is recorded with how it arrived (wp-admin, REST, WP-CLI, cron, a WordPress auto-update, or SiteAgent itself), which user and application password, and where the package came from, so Aura can flag packages an AI agent installed. It only observes; it never blocks an install. Nothing to configure.
- Privacy: each record keeps the user ID, the application password’s name (never the password) and the REST route. While the plugin is active, records older than 90 days (or beyond the latest 200 installs) are deleted; a deactivated plugin cannot delete anything, so they stay until its first cleanup after reactivation (the daily clean-up, an audit or the next install) or until it is uninstalled. Records are not autoloaded and are deleted when the plugin is uninstalled.
2.21.0
- The Aura approval queue now shows whether an operator rule would block or warn about an Elementor design change made through the elementor-mcp plugin (1.38.0 or later), before anyone approves it. Nothing runs when the queue asks. No new settings.
2.20.0
- Rules can now target custom CSS: a rule of type
custom_cssblocks, warns about or allows writes that change a page’s, an element’s or the site kit’s custom CSS, on one page or everywhere. Blocking is cautious: a write that might carry CSS counts. Allowing is strict: only a write the plugin can prove does nothing but set CSS is let through. No new settings; a ruleset without such rules behaves exactly as before.
2.19.3
- A third-party sandbox directory that is a link to a missing or unreachable location is now reported as a link, not as “no sandbox here”. The audit checks for a link before it looks at what the link points to. Read-only; nothing changes on the site.
2.19.2
audit_agent_codenow counts what is in a third-party agent tool’s sandbox store (wp-content/emcp-sandbox):third_party.emcp_sandboxgainsactive(the plugin is loaded) andstore— how many files, how many with an executable extension, and the newest modification date. Until now an empty directory and one holding forty PHP files looked the same to a fleet audit. Counts only: no file is opened and no file name leaves the site. Links are never followed; a sandbox directory that is itself a link is reported as such and not walked. A directory that cannot be read is reported as unreadable, never as empty. Read-only, no settings, nothing changes on the site.
2.19.1
audit_mcp_exposure‘selementor.governorblock reportsproxy_refused_30d— how many times in the last 30 days the door governor turned an authenticated non-browser caller (an Application Password or bearer identity: an agent) away from Elementor’s editor proxy (403 aura_door_proxy_closed, 2.19.0). Anonymous requests get the same 403 but are not counted, so no unauthenticated traffic can write to the site. Same hourly buckets andcounters_as_ofcutoff as the four existing counters;nullwhen the count could not be read.
2.19.0
- Security: Elementor’s editor-internal MCP proxy (
elementor/v1/mcp-proxy) is closed to anything but a browser session while the Aura door governor is active — an Application Password or bearer client is answered403 aura_door_proxy_closedand pointed at the governed/elementor/mcpdoor. Six of the eleven governed Elementor writes were reachable there past the governor since 2.16.0; the editor’s own Global Classes / Variables UI is unaffected. - Security: the door governor’s route matchers are case-insensitive, as WordPress’s REST dispatcher is — a mixed-case spelling of a governed route no longer walks past the transport closer.
audit_mcp_exposure‘selementorblock now reports Elementor 4.3.0-beta3’s kill switch on the token door (switch: theelementor_mcp_enabledoption, absent means off) and which vendored WP MCP adapter andelementor-mcp-composercopies actually resolve on the site (adapter,composer: version and ABSPATH-relative path).
2.18.4
- Security: an empty port after a webhook host (
https://hooks.zapier.com:/hooks/...,hooks.zapier.com:/...) is now read as a URL parser reads it, so such URLs are redacted in plain text too — the case 2.18.3 listed as a known limit. A colon followed by anything but a port and a slash is still not a port.
2.18.3
- Security: redaction now reads a URL the way a browser’s URL parser does. A backslash used as the path separator under http, https, ws, wss, ftp or a protocol-relative prefix (
https://hooks.zapier.com\hooks\catch\1/…, also percent- or HTML-encoded) is redacted whole, including the part after the first backslash that earlier releases left in place. - Security: hostname characters a URL parser normalises away (fullwidth and mathematical letters, the ideographic full stop, zero-width and soft-hyphen characters — Unicode 18.0.0’s IDNA mapping table) are mapped before matching, so
hooks.zapier.comandhooks。zapier.comare redacted likehooks.zapier.com. - A URL parser’s userinfo (
a@b@host, an encoded slash or backslash inside it) and an empty port (host:/) are read as the parser reads them in the backslash and encoded forms above; a plainhttps://host:/pathwith nothing encoded is still matched by the older rule that wants a port digit (tracked as #121). - Redacting a very large field with millions of words now takes about three times the field’s size in memory instead of eighteen.
- Kept as they are: a backslash after a bare host with no scheme, Windows and UNC paths,
file:URLs.
2.18.2
- Security: redaction now decodes HTML references (including the double encoding WordPress itself produces on save and render), percent escapes and JSON escapes before looking for webhook URLs, so encoded or double-encoded Make, Zapier, Slack, Discord, IFTTT or Telegram hook URLs are now redacted.
- The whole encoded word is replaced, not just the part that decoded into a match.
- An encoded word whose host only looks like a webhook host is redacted too.
- More than four encoding layers are replaced as a field.
2.18.1
- Security: receiver URLs are now redacted even when their
/,:or@are percent-encoded or HTML-escaped, including numeric character references left without a trailing semicolon. Before this, an encoded Make, Zapier, Slack, Discord, IFTTT or Telegram hook URL could reach an agent unredacted. - The redaction walk now runs under a total node budget, so a self-referencing payload no longer runs until the request times out; a snapshot payload that exhausts the budget is withheld as
payload: null, payload_redacted: trueinstead. - The gateway’s early placeholder/grant check now only fires for a caller the IP/Origin allowlist and token throttle would already admit, so a throttled or disallowed caller no longer learns whether its token was right.
- A legacy plaintext token is migrated before an MCP-path grant is verified.
2.18.0
- Security: known webhook endpoints no longer leave the site in a REST response an AI agent reads — Aura’s gateway tools, an MCP client using an Application Password, or any logged-in non-browser caller. Make, Zapier, Slack, Discord, IFTTT and Telegram hook URLs, and Elementor Pro form webhooks on any host, are replaced with
aura-redacted:v1:<kind>, including inside Elementor page data and snapshot payloads. People in wp-admin, public visitors and Aura’s own system calls see the real values. - An agent write that carries a redacted placeholder is refused (
aura_redacted_placeholder): leave that field out and the stored value is kept. - Aura’s own page snapshots stay complete: a signed header proves the read is Aura’s (
aura_unredacted_grant_invalidwhen it does not verify). audit_rulesreportsredacted_24handplaceholder_refused_24h;/statusreportsredaction.
2.17.5 and earlier
- WordPress.org truncates a Changelog over 5,000 words, and this plugin’s history is longer than that.
The entries for 2.17.5 and every release before it were moved out of this file verbatim and are kept in full at:
https://github.com/Digitizers/SiteAgent/blob/main/docs/changelog-archive.md
