WordPress plugin intelligence profile

CenterShield – Site Security: Login Protection, 2FA, File Protection & Malware Scan

WordPress security for Japanese sites: login protection, 2FA, file protection and malware scanning, each explained in clear Japanese.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.1.2
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 5.8 · PHP 7.4
Directory statusactive
Last directory update28 Oct 20265d ago
Active installations30Adoption metric — not a quality score
WordPress.org rating5.0 / 5 from 2 ratings
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records CenterShield – Site Security: Login Protection, 2FA, File Protection & Malware Scan version 1.1.2 as active, updated 5d ago and tested up to WordPress 7.1.

Overview

About this plugin

CenterShield is a WordPress security plugin built for Japanese site owners and the

agencies that maintain their sites.

It brings login protection, two-factor authentication, hardening, file protection,

malware scanning and a vulnerability assessment report together in one place. Every setting explains what it protects and

what changes when you turn it on, so you can choose the measures your site needs

without security expertise.

The admin interface and all messages are in Japanese only.

Activating the plugin changes nothing on your site. Press “apply recommended settings”

to enable the recommended set in one step, or turn on each feature yourself.

Account and login protection

  • Login attempt limiting (brute force protection)
  • Username disclosure prevention
  • Custom login URL
  • HTTP Basic authentication on the login screen (written to.htaccess on Apache)
  • reCAPTCHA v2 / v3
  • Two-factor authentication (authenticator app, email, backup codes), with an optional grace period and an option to skip the code for 30 days on trusted devices
  • XML-RPC disabling (signed Jetpack requests are still allowed)
  • IP address restriction for the admin area

Disabling unused features and weak settings

  • Pingback
  • REST API restriction (well known plugins such as Contact Form 7, Jetpack and WooCommerce stay allowed)
  • Author archive pages
  • Theme and plugin file editor, application passwords
  • Unneeded tags in wp_head, such as the WordPress version, the RSD link and emoji scripts

File and server protection

  • Blocking direct access to wp-includes, wp-config.php, configuration and backup files
  • Blocking PHP execution in the uploads folder
  • Disabling directory listing
  • Security headers such as X-Frame-Options
  • Removing publicly readable files such as readme.html
  • Permission review and correction

Ongoing protection

  • Input filtering (lightweight WAF)
  • Comment spam blocking (honeypot, rate limit, previous spam history)
  • Detection of plugins and themes that have gone two years without an update or are not tested with your version of WordPress

Malware scanning

  • Comparison against official checksums for WordPress core and plugins hosted on WordPress.org. Differences limited to comments or line endings are reported as informational
  • Matching against a known vulnerability database
  • Pattern matching against malware signatures bundled with the plugin and updated from the author’s server
  • Change detection against the previous scan, for themes and plugins that are not on WordPress.org
  • Database inspection of posts, widgets and administrator accounts
  • Quarantine, restore from the official original, and difference display

Vulnerability assessment

Checks how your site looks from outside and puts the result into a report you can hand to your client or your team. The checks only send harmless requests to your own site and look up its public DNS records; they never change site data or send attack values to forms.

  • About 50 checks in nine areas: exposed files and information, login and accounts, XML-RPC and REST API, HTTPS and certificates, HTTP headers and cookies, software updates, signs of tampering, email sender authentication (SPF, DMARC, DKIM), and server and WordPress settings
  • Known vulnerabilities in WordPress, plugins, themes and JavaScript libraries, and PHP versions that no longer receive security fixes
  • Each finding is rated on five severity levels, with a CVSS v3.1 score where one applies, a target response time, the expected impact and how to fix it
  • An overall rating in four levels, and a table of what was checked in each area, including the areas with no problems
  • For findings that a CenterShield setting can fix, a link to that setting
  • A printable A4 report with a report number, which you can save as PDF from your browser
  • The last ten results are kept for comparison

External services

This plugin connects to the following external services. No site content, post data

or user data is transmitted to any of them, and every request identifies itself with a

fixed user agent rather than the WordPress default, which would carry your site address.

api.wpcenter.jp (WP Center, the plugin author)

Used to download malware signature definitions and known vulnerability data. The

request is sent when the plugin checks for definition updates and when a scan needs

vulnerability data. What is sent: the plugin version, and the metadata that any web

request carries, namely your server IP address and a fixed user agent string

(“WPCenterSecurity/” followed by the plugin version) that does not contain your site address. What is

received: signature definitions, their digital signature, and vulnerability records.

Your site address and the list of plugins and themes installed on your site are never

sent; matching is performed locally on your site.

jp/plugin-terms/

jp/privacy/

The vulnerability records served from this endpoint originate from Wordfence

, and include CVE records from the MITRE

Corporation. Copyright designations for both are shown with every record in the

scan results, and the Wordfence Intelligence terms are reproduced in

txt inside this plugin. WP Center is not

affiliated with, endorsed by or sponsored by Wordfence or Defiant, Inc.

com/threat-intel/

com/wordfence-intelligence-terms-and-conditions/

com/privacy-policy/

org/Legal/TermsOfUse

api.wordpress.org and downloads.wordpress.org

Used to obtain official checksums during a scan. What is sent: the WordPress version

and locale, and the slug and version of each plugin being verified. What is received:

file checksums.

org/about/privacy/

core.svn.wordpress.org and plugins.svn.wordpress.org

Used only when you press “compare with the original” or “restore the original” on a

scan result. What is sent: the version and file path of the file being retrieved.

org

repository.

org/about/privacy/

www.google.com (reCAPTCHA)

Used only if you enable reCAPTCHA and enter your own keys. The reCAPTCHA script is

then loaded on the forms you select, and the token is verified against Google. What

is sent: the reCAPTCHA token, your secret key and the visitor IP address.

com/terms

com/privacy

Third-party resources

  • Vulnerability data: Wordfence Intelligence Vulnerability Database (https://www.wordfence.com/threat-intel/). Copyright Defiant, Inc. CVE records copyright The MITRE Corporation. Redistributed under the Wordfence Intelligence Terms and Conditions, a copy of which is included in licenses/wordfence-intelligence-terms.txt. Each record displays its copyright designation in the scan results.
  • Original file comparison: the public WordPress.org checksum API and SVN repositories.
  • Part of the malware definitions: Linux Malware Detect (LMD) signatures, Copyright R-fx Networks, GNU GPL v2, https://github.com/rfxn/linux-malware-detect, incorporated under the terms of the GPL. Known malicious domains: URLhaus (abuse.ch, CC0, https://urlhaus.abuse.ch/).
  • QR code generation: qrcode-generator v1.4.4, Copyright (c) 2009 Kazuhiko Arase, MIT License (assets/js/qrcode.min.js).
WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • 2fa
  • firewall
  • login
  • malware
  • security
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 5.8 · PHP 7.4
Update activity28 Oct 20265d ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

Version1.1.11.1.2
WordPress compatibility7.1.37.1.4
Version1.1.01.1.1
Version1.0.91.1.0
Version1.0.81.0.9
Version1.0.71.0.8
WordPress compatibility7.1.27.1.3
Version1.0.61.0.7
Version1.0.51.0.6
Version1.0.41.0.5
Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.