PageForge 1.3 : Vérifiez chaque exécution avant qu'elle n'écrive, mettez à jour les pages générées, les spintox et les lots de reprise. Voir ce qui a changé
CMS ADMINS Security Check Report icon
Activement maintenu Testé avec WP 7.1 #2 in audit

CMS ADMINS Security Check Report

Read-only security audit for WordPress: 62 checks including PHP2Shell, an A to F grade, and a checklist that records what you have fixed.

Installations actives400+100+ niveaux
Téléchargements · 30D1.9K▲ 5× vs prev. 30d
Évaluation5/52 avis
Score de santé77/100Bon
Téléchargements de tous les temps2.8KDepuis septembre 2026
Support résolu—Aucun fil de discussion récent
A besoin deWP 7.0PHP 7.4+
Téléchargements · 7j428▲ +37.2% week over week
Notre verdict

Choix solide

CMS ADMINS Security Check Report is a solid plugin choice in 2026, with a few things worth checking first. It runs on 400+ sites, is rated 5/5 and was last updated 1 week ago, and scores 77/100 on our health check.

  • Développé activement — Dernière mise à jour il y a 1 semaine
  • Testé avec le dernier WordPress (7.1)
  • Momentum — downloads up 395% vs the previous 30 days
  • Petite base d'utilisateurs (400+ installations actives)
  • Très peu de critiques jusqu'à présent

Comment s'accumule-t-il ?

Côte à côte sur les installations, les mises à jour, les évaluations et le support

Téléchargements quotidiens

76152228Aug 22Oct 5Nov 19
Hier36
Moyenne quotidienne (1 ans)8
Jour de pointe30422 Octobre 2026
12 Derniers mois2.7K

Les pics de téléchargement suivent généralement une nouvelle version - chaque site qui met à jour automatiquement compte comme un téléchargement.

Classements

Where CMS ADMINS Security Check R… stands today

WordPress.org Classements de recherche

Position en direct dans la recherche de plugins, Top 100
Mot-cléPositionPlugins concurrentsCatégorie
audit >100 3,362 Best audit plugins →
hardening #23 2,688 Best hardening plugins →
php2shell #1 47 Best php2shell plugins →
scanner #83 1,749 Best scanner plugins →
la sécurité #54 10,000 Meilleurs plugins de sécurité →

Adoption de version

Part de sites actifs par version.

  • 2.581.9%
  • 2.418.1%

Répartition des notes

★★★★★ ★★★★★ 5 sur 2 avis

  • 5★100.0%
  • 4★0.00%
  • 3★0.00%
  • 2★0.00%
  • 1★0.00%

About CMS ADMINS Security Check Report

From the official readme · v2.5.1

Description

Security Check Report looks at 62 aspects of a WordPress installation and turns the findings into a graded report. It changes no setting, no file and no account. It stores its own results in the database, and it writes one temporary file in the uploads folder that is deleted again in the same request.

The report opens with the five things worth doing first, not with a table of 62 rows. Every finding says what was found, why it matters and what to do about it.

There is no Pro version, no licence key, no account and no usage tracking. Apart from api.wordpress.org and your own site the plugin contacts nobody. Before a release the checks run against real sites, and a finding that turns out to be wrong is fixed as a bug: 2.4.0 alone removed seven false alarms.

From the second run onwards the page no longer opens on the start button but on an overview: the grade, a line saying where the site stood on the first run and where it stands today, one bar per recorded run, five tasks to work through, what is still open, and what has been resolved and when.

Each task has a button that runs that one check again and answers within seconds, so a fix is confirmed while you are still on the screen instead of at the next full pass. A single re-check writes no point into the history, and the page says as much, because a grade pieced together from several passes is not a grade measured in one.

PHP2Shell check (CVE-2026-109618, CVE-2026-109619)

PHP2Shell is the name for two critical flaws in the PHP core that let an attacker run code on the server with a single request and no login. The PHP team released the fixes on 21 October 2026, and attacks started the same day. No WordPress plugin can patch PHP itself, but this one tells you within seconds whether your server still needs the update.

The PHP2Shell check reads the PHP version your site actually runs on and answers in plain words:

  • Green: PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35 or newer, or an Ubuntu package that carries the backport. The fix is in place.
  • Orange: the fix cannot be read from the version number. Update PHP, or have your host confirm the backport. Red Hat, Plesk and cPanel often keep the old number after patching, so orange is a question to your host, not a verdict.

Start a run on the Security Check screen or with wp security-check run. The check sends nothing anywhere and only looks at the running PHP.

Ce que vous obtenez

  • A weighted grade from A to F, where one failing critical check cannot be hidden by fifty passing minor ones
  • A checklist of five tasks at a time, derived from urgency and score rather than from guesswork, with the next one moving up when you finish one
  • A button per task that re-runs that single check, so you see the result of a fix in seconds
  • A history of the last 24 runs, with the very first one kept for good, so the starting point stays visible
  • A comparison with the previous run, right under the grade: how many findings are new, how many were resolved and whether the grade moved
  • The shortest way to the next grade: how many tasks it takes and which ones, worked out from the same scoring as the grade itself
  • Milestones with the date you reached them, such as the first grade A or 25 findings resolved, and a count of the months in a row with a full run. Muting a finding never counts towards any of them
  • Muting that remembers what a finding said, so an accepted finding comes back the moment it actually changes
  • “Not determined” as a real outcome, so a blocked request is never reported as a problem and never moves the grade
  • A count on the menu entry, a widget on the dashboard home, the grade in Tools, Site Health, and a reminder once the last run is more than 30 days old
  • Exports as plain text, JSON and CSV
  • A WP-CLI command that produces the same grade as the screen
  • An explanation of every check, searchable, right on the page

What it checks

Core, plugins and themes. WordPress version, PHP version against the published end-of-life dates, whether PHP carries the fix for PHP2Shell (CVE-2026-109618 and CVE-2026-109619), automatic core updates, core file integrity against the official checksums, files in the core directories that are not part of WordPress, pending plugin and theme updates, unused plugins and themes, plugins that look abandoned, plugins whose listing was closed, plugins whose author changed, must-use plugins and drop-ins, other WordPress installations sitting next to this one.

Configuration. Debug mode, debug log exposure, the theme and plugin editor, installing code from the dashboard, authentication keys and salts, table prefix, database user privileges, whether the scheduler actually runs, autoloaded options size, injected content in the options table, backups, login protection, password policy.

Files and permissions. Permissions on wp-config.php, the uploads folder and the core directories, world-writable paths, executable files among the media, whether the server runs PHP from the uploads folder, configuration and backup files that the server hands out, readable .git, .svn and .hg folders, database dumps in the web root, leftovers from interrupted updates, directory listing.

Accounts and access. Guessable passwords, predictable administrator names, how many accounts hold administrator rights and which have gone dormant, roles below administrator holding capabilities they should not have, open registration and the role it hands out, two-factor coverage per administrator, the application password inventory including when each was last used and from where.

Network and transport. HTTPS and the redirect from http, TLS certificate expiry and negotiated protocol, the security headers and their quality rather than their mere presence, cookie attributes, CORS, exposed software versions, legacy discovery tags, XML-RPC, user enumeration, REST routes that accept writes without checking permissions, and whether the client address can be faked through forwarded headers.

Transparency and disclosure. Whether AI-generated content carries a machine-readable label and whether visitors are told when they are talking to an AI system, which Article 50 of the EU AI Act has asked for since 2 August 2026. The disclosure plugins in the directory are recognised by their folder and by the settings they write, so a plugin that was installed and never set up is not mistaken for an answer. A site that publishes no AI output has nothing to label, so this one only ever warns and barely moves the grade.

What it is not

  • Not a firewall. It blocks nothing and intercepts no requests.
  • Not a malware scanner. It compares core files against the official checksums and looks for injected content in the options table, but it does not hunt for signatures in plugin or theme code, and it removes nothing.
  • Not a vulnerability database. It reports that a plugin is outdated, abandoned or delisted; it does not look up individual CVEs. The one exception is PHP2Shell, because it hits every PHP site at once.
  • Not an auto-fixer. Every finding comes with instructions, and you carry them out.
  • Not a monitor. Nothing runs in the background, nothing is scheduled, no mail is sent. A check runs when you start it.

Data and connections

The plugin talks to api.wordpress.org and to your own site. Nothing else, and there is no telemetry. See the questions below for exactly which endpoints and what is stored locally.

Who builds it

CMS ADMINS maintains, hosts and secures WordPress and Drupal sites from Munich. This plugin is the checklist we run ourselves, packaged up. It is free, it stays free, and it works the same whether or not you ever talk to us.

Installation

  1. Install the plugin from the WordPress plugin directory, or upload the folder to /wp-content/plugins/security-check-report.
  2. Activate it on the Plugins screen.
  3. Open “Security Check” in the admin menu and start a run.

The plugin needs PHP 7.4 or newer and WordPress 7.0 or newer. Running the checks requires the manage_options capability, so on a normal site that means an administrator.

Journal de modifications

Shows the way to the next grade and the milestones reached, lets AI assistants read the stored report, and stops Site Health from calling an open critical finding harmless.

Releases before 2.2.0 are listed in changelog.txt.

2.5.1

Added
* The ability security-check-report/get-report for the Abilities API in WordPress 7.0. AI assistants and other tools can read the last run without starting one, and without user names, paths or other raw findings.
* The action cascr_run_completed, fired after every full run with the stored run and its summary.
* Under the grade: how many tasks stand between the site and the next grade, and which ones. Those tasks carry a “Raises the grade” label.
* A line when the grade moved since the run before.
* Milestones with their date: no open critical finding, no failed check, the first grade A, 10, 25 and 50 findings resolved, 3, 6 and 12 months in a row with a full run. Muted findings never count. A site that was checked before starts with what its history already shows, dated when it happened.

Changed
* Three more screenshots: the dashboard widget, Site Health and a single re-check.
* The box at the top is laid out as grade, numbers and action side by side, with the button at the top of its column and the goals in a row of their own underneath. The page header carries the plugin mark.

Fixed
* Site Health said “nothing urgent” for a site at grade A or B while a critical check was open, for instance PHP2Shell as a warning. It now recommends a look for a critical warning and reports a critical failure as critical.

2.5.0

Added
* The grade appears in Tools, Site Health: good for A and B, recommended for C or a run older than a month, critical for D and F. It reads the stored run and never starts a scan.
* A line under the grade says what changed since the run before: how many findings are new and how many were resolved.
* wp security-check run --fail-below=<grade> exits with status 1 when the grade is worse, for pipelines and monitoring.

Changed
* The five tasks are ordered by severity first. A critical warning such as PHP2Shell no longer sits behind a medium failure.
* Each task shows its status next to its severity, so a critical check that is only a warning reads as one.
* Muted findings say so in their badge (“Muted, was Failed”) instead of showing the old status in grey.
* Category progress counts muted checks, so each category shows its full number of checks.
* The progress chart shows the grade above and the date below every bar, newest run first.
* Section headings stand out more, and the list of all checks keeps status, name and summary in aligned columns.
* Screen readers: the progress bar is announced as one, focus moves to the grade after a run, and every task and result button names the check it belongs to. Faint text now meets the WCAG AA contrast ratio.

Fixed
* “WordPress 7.1.3 is outdated, 7.1.3 is available”: an update offer for the installed version no longer counts as an update.
* The readme said a command line run stores nothing. It does, and now the readme says so.

2.4.1

Added
* PHP2Shell check for CVE-2026-109618 and CVE-2026-109619: green when the running PHP is 8.5.12, 8.4.27, 8.3.36, 8.2.35 or newer, or an Ubuntu package with the backport, orange when the fix cannot be read from the version number

2.4.0

Ajoutée

  • A checklist instead of a one-off verdict. From the second run onwards the page opens on an overview: the grade, where the site started and where it stands today, a bar for every run, the five things to work through, what is still open, and what has been resolved and when. The guided three-step walkthrough stays for the first run.
  • Every task carries a button that re-runs that one check and answers within seconds. A fix is confirmed while you are still at the screen, and the next task moves up, instead of waiting for the next full pass.
  • A history of the last 24 runs. The very first one is kept for good, so the opening line can always name where the site started. An installation upgrading from an earlier version finds its two stored runs as the first two points.
  • Progress per category, so it is visible which part of the site has been dealt with and which has not.
  • A sixth area, transparency and disclosure, with one check in it: whether AI-generated content on the site is labelled. Article 50 of the EU AI Act has asked for a machine-readable label and a notice for AI chatbots since 2 August 2026. The disclosure plugins from the directory are recognised by their folder and by the settings they write, and the check only ever warns, because a site with no AI content has nothing to label.
  • A count on the menu entry, a widget on the dashboard, and a reminder once the last full run is older than thirty days. The reminder can be switched off for good, per user.

Modifié

  • The report is built on the server now. It used to be assembled in the browser, which meant the overview could not exist before a run had finished, and the same markup would have had to be written twice.
  • A single re-check never writes a point into the history, and the page says plainly that the grade then rests partly on older measurements. A partial pass is not a run.
  • A run stores what each check reported, so the report can be rebuilt without running everything again.

Fixé

Every check was read against the sources it cites: php.net, the WordPress handbook, core source, MDN, and the packages of the plugins it recognises. That turned up findings that fire on correct configurations, one that could not fire at all, and claims that stopped being true years ago.

  • Sites with two-factor protection were reported as having none. The user meta key stored for iThemes, Solid and Kadence Security is not the one those plugins write, and the one for Defender does not exist in it at all. Google Authenticator stores the string “disabled”, which counted as a second factor because it is not empty, so the one case the check exists for went unnoticed.
  • The check for plugins removed from the directory could not fire. The API answers 404 for a closed listing, and the WordPress function turns that into an error before the “closed” flag is ever read, so the check reported all clear in exactly the case it was written for. It now asks the endpoint itself and tells a closed listing, a plugin that was never listed and an unreachable one apart.
  • WordPress installed in its own directory was reported as an injected option value, at critical severity. Comparing the site and home addresses cannot tell that apart from a takeover, and in a real takeover both are changed together, so the comparison is gone.
  • A site behind Cloudflare was reported as having a spoofable client address. The check now looks for a proxy that identifies itself and says the result is undetermined when it cannot tell, rather than warning.
  • The WooCommerce Store API was reported as a write route left unprotected. Registering a route as public is the spelling the handbook prescribes, so a route with no permission callback at all and one that is deliberately public are now told apart.
  • The strict Content Security Policy from the published guidance was reported as leaving the hole it closes. Browsers that understand ‘strict-dynamic’ ignore the ‘unsafe-inline’ fallback beside it, and the check now does the same. A host wildcard is no longer mistaken for allowing scripts from anywhere.
  • DISALLOW_FILE_MODS closes the file editor and stops background updates. Neither check knew that, so following this plugin’s own advice left one finding standing and turned another into a false all clear.
  • system.multicall has not amplified password guessing since WordPress 4.4, and the XML-RPC check now recognises the filter most security plugins use to switch the interface off.
  • The advice to pick a display name different from the login name does nothing, because the author slug keeps the login name it was generated from.
  • Application passwords were reported as switched off on every site without HTTPS, which is where WordPress refuses them in the first place.
  • A server that hands out the source of a PHP file was reported as running it. Those are different problems with different fixes.
  • .user.ini and .htpasswd were listed among files to delete. They are live configuration, and deleting the second one locks people out.
  • On IIS the check for .htaccess advised saving the permalink settings, which writes web.config there and never an .htaccess.
  • A role that merely appeared since the first run, as a shop or membership plugin does, was reported as a role holding administrator-level power.
  • Installers and shell scripts among the uploads are no longer treated as code the server runs.
  • A run stored by 2.3.2 could raise a PHP warning on the first page view after the update, and the mute state it was saved with is now kept until a run of this version replaces it.
  • Scans and lookups that cannot complete now say so instead of reporting all clear: a core file scan that hit its limit, a plugin listing that could not be retrieved, a database dump whose URL did not answer.

Explanations

  • Every one of the sixty-one entries was read against the method it documents. Fourteen described outcomes the check does not have, or stayed silent about the ones it does.
  • The entry on security headers now names the values to enter, which is the one thing it was missing. The permission entries say where to change file permissions without shell access. Roughly a dozen terms are resolved where they first appear rather than assumed.
  • The warning about the table prefix named the wrong mechanism, and the reasoning for 640 against 440 on wp-config.php was inverted. Files in the web root were called harmless as a group, although phpinfo.php prints the whole PHP environment.

2.3.2

Fixé

  • The check for executable files in the uploads directory reported the empty index.php that WordPress and most plugins drop into every upload folder to stop directory listing. Those files are the opposite of a finding, and because the check counts as critical, a single one of them pulled an otherwise healthy site down to grade D. Across twenty sites the grade was identical for that reason alone. The check now reads such a file instead of judging it by name: an index.php passes only when it stays small and reads no request data, includes no other file, calls none of the functions a dropped shell needs and prints nothing of its own. Everything else is still reported, index.php included.
  • Every reported file now carries its size and, where an index.php did not pass, the reason it was reported. A guard file runs to a few hundred bytes, so the number alone usually settles what a file is.
  • Two-factor coverage could not tell an account that never finished the setup from one it simply could not read, and called both inconclusive. Each supported plugin is now listed together with the user meta it writes, so an installed plugin nobody uses is reported as the exposure it is, naming the accounts without a second factor.
  • Two-factor detection now covers ReportedIP Hive, Solid Security, Kadence Security, WP Defender and Google Authenticator. iThemes Security has been renamed twice and ships under three folder names, all of which are recognised.

2.3.1

  • The screen is now laid out as three steps: start the check, read the result, go through everything else. Steps two and three say what they will contain before the first run, so the page explains itself.
  • The start button says what it does and how long it takes, and the note about the temporary file sits directly above it.
  • The result opens with a plain sentence, not just a letter: how many findings need attention now, how many are worth improving, and how many checks could not be completed.
  • The page scrolls to the result when a run finishes, instead of leaving it below the fold.
  • The priority list is now called what it is, a to-do list, and says to work through it in order.
  • A finding can carry a link to further help. The two-factor finding uses it to point at the Two Factor plugin from the WordPress core team and at ReportedIP Hive, which we build ourselves and name as ours.
  • Removed three interface strings and two stylesheet rules left behind by the rebuild.

Journal des modifications complet sur WordPress.org →

Captures d'écran

The overview from the second run onwards: grade, the way from the first run to today and the next five tasks
The overview from the second run onwards: grade, the way from the first run to today and…
All checks, grouped by area and filterable by outcome, with one finding expanded
All checks, grouped by area and filterable by outcome, with one finding expanded
The built-in documentation for every check, with a search
The built-in documentation for every check, with a search
The dashboard widget with the grade and the number of open tasks
The dashboard widget with the grade and the number of open tasks
The grade in Tools, Site Health
The grade in Tools, Site Health
A task checked again on its own, with the result at the top of the page
A task checked again on its own, with the result at the top of the page

Pour les développeurs

Est-ce votre plugin ? Montrez les chiffres.

Ajoutez un badge en direct à votre site, docs ou github readme. Il se met à jour par lui-même - aucun compte n'est nécessaire.

Badge d'installations actives Badge Badge de score de santé

Best CMS ADMINS Security Check Rep… alternatives

All audit plugins →
Alternatives
Rang Plugin Installations actives Évaluation Mise à jour Santé
1 Audit Trail Audit Trail Audit Trail is a plugin to keep track of what is going on inside your blog by monitoring… de John Godley 20K+ ★★★★★★★★★★ 2.8 (4) il y a 9 ans 30
3 MYAIO – Your AI-Powered Co-Founder MYAIO – Your AI-Powered Co-Founder AI-powered WordPress SEO plugin with real-time audits, smart recommendations, and… by gabrielwillkinson1 400+ ★★★★★★★★★★ Aucun avis Il y a 2 semaines 70
4 Sa11y, the accessibility quality assurance assistant | Accessibility Checker Sa11y, the accessibility quality assurance assistant Geared towards content authors, Sa11y straightforwardly identifies accessibility issues at… by Adam Chaboryk 300+ ★★★★★★★★★★ 5 (1) il y a 4 mois 61
5 Destino Access Audit Destino Access Audit Audit who has access to your site: Application Passwords, admin accounts, and connected… by destinoexterior 100+ ★★★★★★★★★★ Aucun avis Il y a 2 mois 64
6 BCC All Emails BCC All Emails A quick plugin to create an audit trail of emails sent from your site to another email… by watchthedot 100+ ★★★★★★★★★★ Aucun avis il y a 1 mois 64
7 Aipatch Security Scanner Aipatch Security Scanner WordPress security scanner with 36 checks, malware scanning, core integrity verification… by Esteban 100+ ★★★★★★★★★★ Aucun avis il y a 7 mois 47
8 Pluginventory Pluginventory Know exactly which plugins run across your WordPress portfolio — search any plugin… by pluginventoryteam 90+ ★★★★★★★★★★ Aucun avis il y a 5 mois 46
9 Content Audit Content Audit Lets you create a content inventory right in the WordPress Edit screens. You can mark… Par Stéphanie Leary 70+ ★★★★★★★★★★ 4.5 (8) Il y a 7 ans 35
10 Post Author IP Post Author IP Records the IP address of the original post author when a post first gets created. de Scott Reilly 60+ ★★★★★★★★★★ Aucun avis Il y a 5 ans 25
11 Auditizer – AI Website Audit & Optimization Auditizer – AI Website Audit & Optimization AI-powered SEO and accessibility auditing. Scan, fix, and optimize your WordPress content… by Teamjuh 50+ ★★★★★★★★★★ 5 (1) il y a 8 mois 47

FAQ

CMS ADMINS Security Check Report: quick answers

Réponses directes, extraites des données en direct WordPress.org.

Source : WordPress.org

Is CMS ADMINS Security Check Report free?

Yes. CMS ADMINS Security Check Report is free to download and use from the official WordPress.org plugin directory.

Is CMS ADMINS Security Check Report safe to use in 2026?

CMS ADMINS Security Check Report is a solid plugin choice in 2026, with a few things worth checking first. It runs on 400+ sites, is rated 5/5 and was last updated 1 week ago, and scores 77/100 on our health check.

How many websites use CMS ADMINS Security Check Report?

CMS ADMINS Security Check Report is active on 400+ WordPress websites and has been downloaded 2,793 times since it launched in September 2026. It was downloaded 1,896 times in the last 30 days.

Does CMS ADMINS Security Check Report work with WordPress 7.1?

Yes. The developer has tested CMS ADMINS Security Check Report up to WordPress 7.1.5, the latest release. It requires WordPress 7.0 or newer.

What PHP version does CMS ADMINS Security Check Report need?

CMS ADMINS Security Check Report requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.

When was CMS ADMINS Security Check Report last updated?

The latest version, 2.5.1, was released on November 10, 2026 (1 week ago).

Who makes CMS ADMINS Security Check Report?

CMS ADMINS Security Check Report is developed and maintained by Patrick Schlesinger.

What are the best alternatives to CMS ADMINS Security Check Report?

The most popular alternatives to CMS ADMINS Security Check Report are Audit Trail (20K+ installs), MYAIO (400+ installs) and Sa11y, the accessibility qu… (300+ installs).

Propulsé par PageForge

Un modèle et une feuille de calcul. Une vraie page pour chaque recherche.

PageForge transforme chaque ligne d'un CSV en une page WordPress avec son propre titre, URL, SEO et schéma, construit sur la mise en page que vous Déjà conçu. Gratuit sur WordPress.org.

  • CSV et XLSX, plus Google Sheets sur les professionnels et les entreprises
  • Son propre titre, URL, SEO champs et schéma pour chaque page
  • Fonctionne avec l'éditeur de blocs, Elementor, Divi et Avada
  • Gratuit sur WordPress.org, pas de carte de crédit

↑↓ bouger↵ ouvrir