ATV Web Security icon
Actively maintained Tested with WP 7.1

ATV Web Security

Block persistent changes on a compromised WordPress site — with optional AI-assisted false-positive filtering.

Active installs<10New
Downloads · 30d544• 0% vs prev. 30d
Rating—0 reviews
Health score64/100Good
All-time downloads537Since Oct 2026
Support resolved—No recent threads
RequiresWP 6.0PHP 8.0+
Downloads · 7d39▼ -75.8% week over week
Our verdict

Solid choice

ATV Web Security is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 2 weeks ago, and scores 64/100 on our health check.

  • Actively developed — last update 2 weeks ago
  • Tested with the latest WordPress (7.1)
  • Small user base (<10 active installs)
  • Very few reviews so far

How does it stack up?

Side-by-side on installs, updates, ratings & support

Daily downloads

173451Oct 19Nov 1Nov 15
Yesterday6
Daily average (1y)19
Peak day69Nov 5, 2026
Last 12 months544

Download spikes usually follow a new release — each site that auto-updates counts as a download.

Rankings

Where ATV Web Security stands today

WordPress.org search rankings

Live position in the plugin search, top 100
KeywordPositionCompeting pluginsCategory
AI >100 8,184 Best AI plugins →
malware >100 524 Best malware plugins →
protection >100 6,753 Best protection plugins →
security >100 10,000 Best security plugins →
two factor >100 770 Best two factor plugins →

About ATV Web Security

From the official readme · v1.0.53

Description

ATV Web Security puts your WordPress website into a “protected” state where visitors can still read and use the site, but nothing can persist changes to it — not plugins, not compromised administrators, not direct database access, and not a PHP shell.

AI-assisted false-positive filtering (new in 1.0.51). Detection is only useful if you can tell an attack from WordPress doing its job. ATV Web Security can send metadata about a finding to Groq, using your own free API key, and show a plain-language verdict beside it: benign, suspicious or unknown, with a confidence, a risk level and a one-sentence reason. New files are reviewed as they are found; intrusion events can be reviewed with one click or automatically every five minutes. The verdict appears in the Integrity tab, the intrusion log and the dashboard widgets, so the answer sits next to the finding. The feature is optional, off by default, metadata-only, advisory and fail-open — see “AI false-positive filtering (Groq)” below for setup, payload and limits.

How it works — multiple independent layers:

  • WordPress protection — plugin/theme/core operations, file editors, user creation, option writes and administrator actions are intercepted and denied.
  • Database protection (manual) — revokes the database account’s write privileges at the MySQL/MariaDB server level through a separate privileged account, keeping row-level INSERT/UPDATE/DELETE for allowed flows. The site account’s own GRANT authority is never consumed, and an SQL firewall blocks writes when privileges cannot be changed. No tier turns this on.
  • Filesystem protection (manual) — makes wp-config.php and .htaccess read-only and marks them plus the signing key immutable with chattr where supported, restoring the original permissions when switched off. wp-admin, wp-includes, plugins and themes stay writable so WordPress can update, with changes caught by integrity monitoring and the new-file watch. No tier turns this on.
  • Upload protection — executable uploads are blocked by extension, MIME and content, and the uploads directory is hardened so scripts cannot execute there.
  • API protection — REST, AJAX, XML-RPC, WP-CLI and cron-based mutation is blocked; reads remain available.
  • PHP firewall integration — a small mu-plugin rejects traffic under wp-includes, blocks links to private files and neutralises low-level PHP tricks.
  • Integrity monitoring — baseline hashes of core, configuration and plugin files are verified periodically and on demand.
  • New-file and new-table watch — a scheduled scan reports files and database tables that were not there before. Each finding shows the path, detection time and size, with Dismiss and Delete after review; anything a WordPress core, plugin, theme or translation update explains is listed with its cause instead of being announced. Installs and updates performed outside WordPress are recognised too. Scan interval, email delivery and recipients are set on the Integrity tab.
  • AI false-positive filtering (optional) — sends file-change and intrusion-event metadata to Groq with your own API key and labels each finding benign, suspicious or unknown with a confidence, risk level and one-sentence reason. Reviews are advisory: nothing is deleted, quarantined, blocked or dismissed automatically, every request fails open, and the feature stays off until you add a key.
  • Access rules (optional) — AbuseIPDB-powered IP reputation blocking and a login-country rule, both off by default, with an IP/CIDR allowlist, fail-open lookups and caching.
  • Backend lock — the plugin has its own top-level menu; once protection is ON and a master password is set, the settings stay behind a lock screen until that password is entered (12-hour unlock, forged-cookie safe, brute-force rate limited). The master password accepts 8-64 letters, digits and symbols and is the single password accepted to turn protection OFF.
  • Email verification code (Two-Factor, optional) — a six-digit code emailed to administrators in addition to the WordPress password, entered on the login form itself. Codes last 10 minutes, can be resent once a minute (five per quarter hour), and the account locks for 15 minutes after five wrong entries. If the mailer cannot deliver, login stays blocked on purpose; recover with wp atvws otp disable.
  • Passkeys / WebAuthn (optional) — registers a hardware-backed credential with Windows Hello / TPM, Touch ID, a phone or a security key. The private key never reaches the site, a cookie, JavaScript or a backup. With enforcement on, protected administrator logins are accepted only from a device whose passkey verifies; an account with no passkey is never blocked, and recovery stays available. A passkey also satisfies the device lock and replaces the emailed code.
  • Trusted device lock (optional) — binds protected actions to one computer with a one-time token in a secure HttpOnly, SameSite cookie. Other computers get a “link your device” screen that requires the master password, and linking/unlinking always requires it. The Recovery tab stays reachable, so a lost device cannot lock the owner out permanently.
  • Behavior policy (optional) — scores privileged activity per source IP over 24 hours and locks the session when the risk crosses a threshold: failed unlock (15), failed disable attempt (25), failed restore attempt (20), failed login (20), refused passkey login (10). The owner is never scored and can clear a lock with the master password.
  • Cryptomining defence — strips miner script tags from rendered pages, refuses WordPress HTTP requests to pool domains, scans wp-content for native executables and miner markers, and searches posts and options for injected script blocks. The scans are report-only; nothing is quarantined by a heuristic match.
  • Detection & monitoring — a signed login-page script/stylesheet baseline, a self-probe for exposed backups, dumps, dotfiles and debug logs, honeypot decoys with escalating temporary bans, and a local inventory of outdated, abandoned or delisted plugins and themes.
  • Snapshot backup and restore — a signed copy of every file WordPress can change plus a full database dump with real CREATE TABLE schema. A snapshot is only saved after it validates row dumps, row counts and a working siteurl. Keep unlimited named snapshots plus automatic ones — daily, weekly, monthly, chosen weekdays or off — and delete the automatic copies in one click without touching the current or named snapshots. Nothing is deleted automatically. Restore requires protection and both manual write locks to be off, refuses a damaged or incomplete snapshot, quarantines extra files, drops extra tables, replays every row in a transaction and rolls back with the exact MySQL error on failure.
  • Live progress — snapshot create, snapshot restore and integrity scans show a stage, item count and percentage while the operation runs.
  • Total protection score — one number out of 100 on the Dashboard and on every screen. Points are earned only for verified active settings, so the score drops when a layer stops working, and the Dashboard lists what is still pending, what it is worth and which tab fixes it.
  • Setup tour — a guided walkthrough through Diagnostics, Set protection level, Snapshot and the remaining configuration screens.
  • Clear layout — screens are grouped into Everyday, Configure, Check and Incident, with a live protection badge, plain-language button descriptions and destructive actions separated from safe ones.
  • Recoverable — reset a forgotten master password from the plugin’s runtime directory (emergency-reset.key + emergency-reset.php) or with wp atvws password reset. Both sign out every session and are logged. WordPress account passwords can only be reset from WP-CLI, and email-code settings can be switched off with wp atvws otp disable.

Protection tiers:

  • MEDIUM and STRONG apply the same WordPress-level layers: WordPress, REST, AJAX, XML-RPC, upload, PHP shielding, integrity, CLI and cryptomining defence. Neither touches database grants or file permissions.
  • LIMITED means protection is on but a core layer is switched off or failed to verify; the dashboard shows which one.

Database and filesystem write protection are separate manual switches on the Dashboard. No tier turns them on, and changing tiers leaves them as they were; both require protection to be on. The database lock revokes write grants where a privileged MySQL account is configured (the wizard or ATVWS_DB_ADMIN_* constants) and reports partial when only the SQL firewall applies; the site account’s GRANT authority is never consumed. The filesystem lock makes wp-config.php and .htaccess read-only and marks them plus the signing key immutable via chattr where available, restoring the original modes when switched off. wp-admin, wp-includes, plugins and themes stay writable so WordPress can update, with changes reported by integrity monitoring and the new-file watch.

Choosing or changing a tier requires the master password, so a hijacked admin session cannot quietly weaken the site. Every layer also has its own switch for fine-tuning, and picking a new tier resets those switches. The old names STANDARD, AUTO and HARDENED still work and map to Medium and Strong.

Allowed writes:

Persistent visitor flows (comments, contact forms, WooCommerce, user registration) are BLOCKED by default. Re-enable only what the site needs from the “Allowed Writes” page; everything else stays blocked.

Turning protection OFF is deliberately difficult: submit a form, confirm a checkbox, type the exact phrase and re-enter your account password (plus an optional passphrase). Emergency recovery paths (WP-CLI, a wp-config constant, a recovery file or manual panel instructions) are documented in docs/RECOVERY.md.

AI false-positive filtering (Groq)

ATV Web Security can ask an AI model to review a finding and suggest whether it looks like ordinary activity or deserves a closer look. The feature is optional, off by default, and uses your own Groq account: there is no shared key and no request is paid for or proxied by the plugin author.

It reviews new files that no WordPress, plugin, theme or translation update explains, and intrusion events (BLOCKED, DETECTED or BYPASSED) that the plugin cannot judge with a deterministic rule. Every review returns benign, suspicious or unknown, a confidence percentage, a risk level and a one-sentence reason, shown beside the file on the Integrity tab and beside the event in the intrusion log.

Reviews are advice, not action. Nothing is deleted, quarantined, blocked, dismissed or emailed differently because of a review. The optional “Auto-explain high-confidence benign files” switch only changes how an alert is presented after its confidence threshold is met, and Dismiss and Delete remain manual.

How to configure it:

  1. Create a free API key at https://console.groq.com/keys.
  2. Open ATV Web Security → Integrity and find the AI false-positive filtering (Groq) card.
  3. Paste the key into Groq API key, tick Enable AI triage, leave Model on Automatic — best free model (or choose any model your key can access), then click Save AI settings.
  4. Click Test connection. The plugin validates the key against Groq’s model list and tests a model the account can actually use, so a retired model id does not fail silently.
  5. Choose Review new files and Review intrusion events. Intrusion review mode is On demand by default, which adds a Show AI review button to each unreviewed event; Automatic runs a background review every five minutes.
  6. Click Triage pending now to label findings already waiting.

What is sent — metadata only:

  • New file: path relative to the installation, extension, directory, size, modification time, and whether it is in uploads, a known cache directory, plugins or themes.
  • Intrusion event: outcome, layer, action, target (150 characters, with query values named token, key, nonce, password, pass or auth replaced by [REDACTED]), target kind, static-asset and plugin/theme/uploads flags, whether a user was attached, role, hour of day, and an HMAC-SHA256 hash of the IP address.

Never sent: file contents, POST bodies, database rows, usernames or passwords, raw IP addresses, or any other site content.

Reliability and limits:

  • Every request fails open. If Groq is unreachable, the key is rejected or the daily quota (100 requests by default) is reached, alerts stay exactly as they were and the card shows the last error.
  • After an HTTP 429 the plugin pauses requests for 90 seconds and writes one warning per distinct failure per 30 minutes instead of flooding the Security Log.
  • Reviews are cached per finding, so nothing is re-sent on every run; labels from older prompts are refreshed automatically. Clearing Enable AI triage stops all requests.

See External services below for the data-processing details and Groq’s terms and privacy policy.

External services

This plugin can connect to two external services. Both are optional and off by default, and each is used only while the corresponding feature is on: AbuseIPDB for IP intelligence and Groq for AI-assisted false-positive filtering.

AbuseIPDB

AbuseIPDB provides an IP reputation and geolocation look-up for the site-wide IP reputation block and the login country check, only when those features are switched on. The visitor’s IP address and your AbuseIPDB API key are sent when a protected request is checked. No other data is sent. Lookups are rate-limited and cached; if a lookup fails, the request is allowed (fail-open) and the failure is logged.

This service is provided by “AbuseIPDB LLC”.

  • Terms of use: https://www.abuseipdb.com/legal
  • Privacy policy: https://www.abuseipdb.com/privacy

Groq

Groq provides the hosted language model behind the optional AI false-positive filtering feature, used only after you paste your own Groq API key on the Integrity tab and enable AI triage. The plugin author does not run a proxy, hold a shared key, or receive the data.

Groq runs an inference service for open language models. The plugin sends metadata about one finding and receives a JSON review: verdict, confidence, risk level and a one-sentence reason, stored beside the finding. No result is required for the site to work; if a request fails, the finding stays as it was and the failure is logged (fail-open).

Data sent: your API key in the request header, plus the metadata described in the AI section above — for a new file, the relative path, extension, directory, size, modification time and location flags; for an intrusion event, the outcome, layer, action, target (150 characters, secret query values redacted), target hints, user/role flags, hour of day and an HMAC-SHA256 hash of the IP address. No file contents, POST bodies, database rows, usernames, passwords, raw IP addresses or other site content are sent. Calls stop at 100 per day by default and pause after HTTP 429.

This service is provided by “Groq LLC”.

  • Terms of use: https://console.groq.com/docs/legal/services-agreement
  • Privacy policy: https://groq.com/privacy-policy
  • API keys: https://console.groq.com/keys

Installation

  1. Upload the atv-web-security folder to /wp-content/plugins/.
  2. Activate the plugin through the Plugins screen.
  3. Under the new top-level “ATV Web Security” admin menu, follow the setup tour: review the Diagnostics tab, then click “Turn ON Protection”.
  4. Store the recovery token that is displayed once.
  5. Configure “Allowed Writes”, “Protected Admins” and “Two-Factor” to match your site.
  6. Optional: connect AI triage from the Integrity tab — paste a Groq API key, choose what to review, save, then click “Test connection”. Leave it unconfigured to keep AI triage off. Details in the “AI false-positive filtering (Groq)” section above.

More detail: docs/INSTALL.md and docs/CONFIGURATION.md.

Changelog

Fixes an infinite recursion in the database query filter that could exhaust memory and flood the PHP error log while the database write lock was on. Recommended update.

1.0.53

  • Fixed an infinite recursion in the database query filter. Reading the protection state consults the database mirror, and that read was itself passing back through the SQL firewall; with a cold options cache every level issued the same SELECT until the request exhausted memory and the PHP error log filled. The state is now read once per request and guarded against re-entry, so the firewall can no longer call itself. Sites with the database write lock switched on should update.

1.0.52

  • Automatic backups are now configurable. On the Snapshot tab you can choose daily, weekly (a specific weekday), monthly (a specific day of the month, including “last day”) or any combination of calendar weekdays. Every run happens at 03:23 in the site’s own timezone.
  • Automatic backups can be switched off from the same card. Turning them off keeps the snapshots already stored.
  • Added “Delete automatic backups”, which removes only the automatic snapshots and leaves the current recovery snapshot and every named snapshot untouched.
  • The schedule is stored in the signed state file, and the cron event is re-armed automatically if it is ever removed. Existing daily schedules keep working and are converted on the next admin page view.

1.0.51

  • Added AI-assisted filtering for new file changes and intrusion log events via Groq (metadata only, opt-in, fail-open). New files are reviewed automatically during the scan; intrusion events are reviewed on demand, with a background pass that still labels routine noise without spending an API call.
  • Intrusion events the plugin can judge without a model are now labelled as noise automatically: blocked WordPress cron scheduling and blocked writes to cron, recently_activated or transient options, plus new files that a recorded core, plugin, theme or translation update explains. A webshell-style file name is never explained away by an update.
  • The intrusion log now has a “Show AI review” button on each unreviewed event and a “Review pending events on this page” button, and the AI card offers an Intrusion review mode: On demand (default) or Automatic. The AI review request itself now also tells the model whether the target is a URL, a path or an identifier, whether it is a static asset, and whether it sits in plugins, themes or uploads.
  • AI triage now stops at the first quota, key, model or rate-limit error instead of retrying the rest of the batch, pauses calls for 90 seconds after HTTP 429, and writes one warning per distinct failure per 30 minutes with the API error in the message, so a failing key no longer floods the Security Log with identical rows.
  • The AI model is picked automatically from the free models the Groq account actually has access to, and the selected model is honoured when one is chosen manually.
  • Test Connection now validates the API key against Groq’s model list and tests only models available to the account, so a retired model id no longer produces an unexplained HTTP 404.
  • Fixed HTTP 400 “Failed to validate JSON” with reasoning models such as openai/gpt-oss-120b: the connection test no longer caps the reply at 10 tokens, reasoning effort is lowered for those models, and both the test and triage retry once without strict JSON mode if Groq rejects the generation. Every prompt now contains the word JSON, which Groq requires in JSON mode, and the “must contain the word ‘json'” rejection is retried the same way.
  • Fixed AI triage never running: the background job and “Triage pending now” aborted on an internal property access, so no file or event ever received a review. Triage also no longer re-reviews the same newest events on every run.
  • The Intrusions tab now renders the AI Review cell (verdict, confidence, reason) instead of an empty column, and the New files cards on the Integrity tab and WordPress dashboard show the AI verdict once triage has run.
  • AI triage failures are no longer silent: the AI card shows whether triage is on, whether a key is saved, the last triage run, the next scheduled run and the last error, and both tabs explain why a finding is still pending (AI off, no key, or the exact API error). “Triage pending now” reports the error instead of claiming there was nothing to review.
  • Fixed the AI key appearing unconfigured after saving, keys left double-encoded by earlier builds now read as “not configured” instead of sending garbage to Groq, and the AI test buttons work.
  • AI reviews now carry protection context: a BLOCKED write (including WordPress’s own cron and option updates) is treated as the protection working, not as an attack, so those events are labelled noise or low risk with confidence capped at 70. The AI is no longer allowed to invent users, accounts, IPs, plugins, CVEs or file contents it was not given.
  • File reviews now report a risk level and an action hint, and old reviews are refreshed automatically: bumping the review version makes the next triage run replace labels produced by earlier prompts.
  • Intrusion reviews now show the risk level and the suggested action (no action needed, review, investigate now) next to the verdict.
  • New files are now AI-reviewed during the scan that finds them (up to three per scan), so the alert table and the notification email carry the verdict instead of “Pending triage”. The scheduled triage still reviews the rest and retries failures.
  • Notification emails now wait about two minutes and re-check update causes before sending. Files written while a theme or plugin update is still copying are therefore explained by the completed update instead of being emailed as a possible intrusion.
  • On the Integrity tab, files explained by an update no longer show “Pending triage” in the AI review column, and unexplained files are listed above the explained ones.
  • Redesigned the Integrity tab: settings and watch status now sit side by side with file, table and finding totals, the new-file and new-table alerts use full-width tables with the file name, relative folder, cause and AI verdict in separate columns, and the integrity, quarantine, cleanup and AI controls are grouped into clearly titled cards. Paths inside the installation are shown relative to the site root so long absolute paths no longer dominate the table.

1.0.49

  • Fixed the new-file alert overlapping the Cause/Action columns on the Dashboard and Integrity tabs: file paths in alert tables contain no spaces, so they could not wrap and stretched the table. Paths now break inside their own cell, including in the wp-admin notice and the WordPress dashboard widget.

1.0.48

  • Fixed snapshot restore leaving the site with “One or more database tables are unavailable. The database may need to be repaired.” Every table is now emptied and refilled inside a transaction (InnoDB), every inserted row is checked, the restored options table must contain a non-empty siteurl, and any failure rolls the database back instead of being reported as a successful restore. The repair page could never fix this because the missing row was siteurl itself.
  • Snapshots now store the real CREATE TABLE statement for every table. The previous code wrote only the table name into each schema file, so a table that had been deleted could never be recreated.
  • Snapshot creation now refuses to save an incomplete backup: it verifies that every row dump decodes, that the row counts match, and that siteurl is present.
  • Extra files are now actually removed during a restore. The whole web root (not just .php/.txt) and wp-content drop-ins are covered, anything not in the snapshot is moved to the quarantine folder, and files that cannot be moved are reported instead of silently skipped.
  • Extra database tables are dumped to a restore-audit folder and then dropped, with each DROP checked. Tables present in the snapshot but missing from the site are recreated from the stored schema.
  • Restore is refused while protection or the Database/Filesystem write lock is on. Those locks were silently blocking the DROP/CREATE and file writes a restore needs, which is why extras survived and tables came back empty. Turn both off before restoring.

1.0.47

  • Dashboard layout pass to match the approved design: a wider left column, roomier cards and table rows, pastel hero stat tiles, card-style pending items with numbered circles, and the Save menu setting button moved into the Plugins menu card header.
  • Integrity now sits on the second navigation row beside Miners, Intrusions, Security Tests, Security Logs and Recovery.

Full changelog on WordPress.org →

For developers

Is this your plugin? Show off the numbers.

Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.

Active installs badge Rating badge Health score badge

Best ATV Web Security alternatives

All AI plugins →
Alternatives
Rank Plugin Active installs Rating Updated Health
1 Elementor Website Builder – more than just a page builder Elementor Website Builder – more than just a page builder The Elementor Website Builder has it all: drag and drop page builder, Atomic Editor, pixel… by Elementor 10M+ ★★★★★★★★★★ 4.5 (7.3K) 7 days ago 92
2 Jetpack – AI Agents & MCP, Security, Backup & Analytics Jetpack – AI Agents & MCP, Security, Backup & Analytics Connect ChatGPT, Claude, or another AI agent to your site. Plus backup, malware scan… by Automattic 3M+ ★★★★★★★★★★ 3.7 (2.4K) 2 weeks ago 90
3 All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights) All in One SEO AIOSEO is the WordPress SEO plugin. Boost SEO rankings with AI SEO tools, schema, meta… by Syed Balkhi 2M+ ★★★★★★★★★★ 4.7 (5.2K) 2 days ago 96
4 AI Agent by SiteGround AI Agent by SiteGround Manage all your WordPress sites from one AI chat. Create content, run your WooCommerce… by SiteGround 1M+ ★★★★★★★★★★ 1.7 (98) 4 days ago 67
5 Premium Addons for Elementor – AI-Ready Elementor Addons, Widgets & Templates Premium Addons for Elementor 90+ Elementor widgets & addons, 600+ templates, Mega Menu, WooCommerce, Display Conditions… by Leap13 600K+ ★★★★★★★★★★ 4.9 (1.7K) 4 days ago 97
6 Members – Membership & User Role Editor Plugin Members – Membership & User Role Editor Plugin The best WordPress membership and user role editor plugin. Edit roles, restrict content… by Blair Williams 300K+ ★★★★★★★★★★ 4.9 (1.3K) 2 days ago 93
7 Angie – Agentic AI Angie – Agentic AI Build anything your site needs. Manage it through an agentic AI conversation inside… by Elementor 100K+ ★★★★★★★★★★ 3.3 (20) 1 month ago 69
8 Disable Comments Disable Comments Disable, hide, bulk-delete & auto-reply to comments and WooCommerce reviews —… by rbplugins 100K+ ★★★★★★★★★★ 3.8 (25) 1 week ago 90
9 AI Engine – MCP Server & AI Chatbot for WordPress, with Claude, ChatGPT & Gemini AI Engine The AI chatbot, AI agent and MCP server for WordPress. Connect OpenAI, Claude, Gemini and… by Jordy Meow 90K+ ★★★★★★★★★★ 4.9 (878) 4 days ago 96
10 MCP Adapter MCP Adapter Expose WordPress abilities as Model Context Protocol (MCP) tools, resources, and prompts… by WordPress.org 70K+ ★★★★★★★★★★ 5 (1) 1 month ago 81

FAQ

ATV Web Security: quick answers

Straight answers, pulled from live WordPress.org data.

Live data from WordPress.org · checked Nov 16, 2026

Is ATV Web Security free?

Yes. ATV Web Security is free to download and use from the official WordPress.org plugin directory.

Is ATV Web Security safe to use in 2026?

ATV Web Security is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 2 weeks ago, and scores 64/100 on our health check.

How many websites use ATV Web Security?

ATV Web Security is active on <10 WordPress websites and has been downloaded 537 times since it launched in October 2026. It was downloaded 544 times in the last 30 days.

Does ATV Web Security work with WordPress 7.1?

Yes. The developer has tested ATV Web Security up to WordPress 7.1.4, the latest release. It requires WordPress 6.0 or newer.

What PHP version does ATV Web Security need?

ATV Web Security requires PHP 8.0 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.

When was ATV Web Security last updated?

The latest version, 1.0.53, was released on November 5, 2026 (2 weeks ago).

Who makes ATV Web Security?

ATV Web Security is developed and maintained by atvsoftwarelabs.

What are the best alternatives to ATV Web Security?

The most popular alternatives to ATV Web Security are Elementor Website Builder (10M+ installs), Jetpack (3M+ installs) and All in One SEO (2M+ installs).

Powered by PageForge

Want thousands of pages that rank like these? Build them in an afternoon.

This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.

  • CSV, Google Sheets & API data sources
  • AI content, schema & internal links per page
  • Works with Elementor, Gutenberg, Yoast & Rank Math
  • Free on WordPress.org — no credit card
Sarah is here to help!
Hi there! 👋 Need help finding what you're looking for?
Sarah
Sarah
Online & Ready to Help
Hi there! 👋 Need help finding what you're looking for?

We'll use this to continue our conversation

Just now ✓ Verified

Join 500+ SEO Pros Scaling Their Strategy

Get exclusive programmatic SEO tactics, AI content workflows, and the latest PageForge updates delivered straight to your inbox. Stay ahead of the algorithm.

We care about your data in our privacy policy.