Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3736171,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3736171,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3736171,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3736171,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3736171,"resolution":"1","location":"assets","locale":"","width":1232,"height":1245},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3736171,"resolution":"2","location":"assets","locale":"","width":1232,"height":859},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3736171,"resolution":"3","location":"assets","locale":"","width":1232,"height":794},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3736171,"resolution":"4","location":"assets","locale":"","width":1232,"height":1273},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3736171,"resolution":"5","location":"assets","locale":"","width":1232,"height":1187},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3736171,"resolution":"6","location":"assets","locale":"","width":1232,"height":2340}},"screenshots":{"1":"Overview with the current posture, configuration score and measured activity.","2":"Local file scanner for supported files, pattern findings and baseline comparisons.","3":"Threat activity with local event evidence and filters.","4":"Firewall controls with monitor and blocking choices.","5":"Ban and allowlist management.","6":"Included security controls and their management links."}},"plugin_section":[],"plugin_tags":[1174,31093,1229,55021,600],"plugin_category":[54],"plugin_contributors":[281452],"plugin_business_model":[],"class_list":["post-374999","plugin","type-plugin","status-publish","hentry","plugin_tags-firewall","plugin_tags-hardening","plugin_tags-login-security","plugin_tags-malware-scanner","plugin_tags-security","plugin_category-security-and-spam-protection","plugin_contributors-zeismodev","plugin_committers-zeismodev"],"banners":{"banner":"https:\/\/ps.w.org\/zeismo-security\/assets\/banner-772x250.png?rev=3736171","banner_2x":"https:\/\/ps.w.org\/zeismo-security\/assets\/banner-1544x500.png?rev=3736171","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/zeismo-security\/assets\/icon-128x128.png?rev=3736171","icon_2x":"https:\/\/ps.w.org\/zeismo-security\/assets\/icon-256x256.png?rev=3736171","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/zeismo-security\/assets\/screenshot-1.png?rev=3736171","caption":"Overview with the current posture, configuration score and measured activity."},{"src":"https:\/\/ps.w.org\/zeismo-security\/assets\/screenshot-2.png?rev=3736171","caption":"Local file scanner for supported files, pattern findings and baseline comparisons."},{"src":"https:\/\/ps.w.org\/zeismo-security\/assets\/screenshot-3.png?rev=3736171","caption":"Threat activity with local event evidence and filters."},{"src":"https:\/\/ps.w.org\/zeismo-security\/assets\/screenshot-4.png?rev=3736171","caption":"Firewall controls with monitor and blocking choices."},{"src":"https:\/\/ps.w.org\/zeismo-security\/assets\/screenshot-5.png?rev=3736171","caption":"Ban and allowlist management."},{"src":"https:\/\/ps.w.org\/zeismo-security\/assets\/screenshot-6.png?rev=3736171","caption":"Included security controls and their management links."}],"raw_content":"\n
ZEISMO Security combines a WordPress firewall, malware scanner, login protection and practical hardening in one local security console.<\/p>\n\n
The plugin starts in monitor mode. It inspects suspicious request patterns and records evidence without blocking visitors. After reviewing the activity on your own site, you can enable blocking by attack category.<\/p>\n\n
Run a local scan to review suspicious PHP, JavaScript, iframe, redirect and spam patterns in supported files. Integrity checks compare file hashes with a locally recorded baseline to identify additions, modifications and removals. They do not compare every file against an official clean-copy database. Review the site before accepting a new baseline.<\/p>\n\n
Scans cover supported readable files in wp-admin, wp-includes, the plugins directory and the active theme root. Uploads, the database and root-level files are outside these scan roots. Files over 2 MB, unsupported extensions and symbolic links are excluded. A result with no findings is not proof that the entire website is clean.<\/p>\n\n
New installations begin in monitor mode so administrators can inspect real activity before deciding which categories to block. Review the measured local activity and scan coverage before changing settings.<\/p>\n\n
The WordPress.org edition runs its available security controls on your own WordPress site. No account, licence token or remote ZEISMO service is required. Local features in this edition are not restricted by a paid plan.<\/p>\n\n
Blocking is disabled by default. Logged-in editors are excluded from firewall enforcement, and the request filter fails open if it cannot evaluate a request. No security plugin can guarantee that a site will not be compromised.<\/p>\n\n
Read the complete user guide<\/a> | Product information<\/a><\/p>\n\n This WordPress.org distribution performs its security analysis on the WordPress site where it is installed. It does not contact ZEISMO, load remote code, check a ZEISMO licence, send source files to ZEISMO or include a separate updater.<\/p>\n\n The plugin stores security settings and local security records in the site's WordPress database. Records can include request paths, browser user-agent strings, usernames used in login attempts, pseudonymous IP hashes and, when enabled, raw IP addresses. Raw IP storage is enabled by default so administrators can investigate and block attacks. Administrators can disable raw IP storage or anonymise logged addresses in Settings.<\/p>\n\n Security events follow the retention period selected by the administrator. Raw event IP addresses are removed after 90 days even when a longer event-retention period is selected. Optional critical alerts are sent with the site's configured WordPress mail system and are disabled by default.<\/p>\n\n Deactivation feedback is optional, stays in the site's WordPress database and is not sent to ZEISMO. Deactivating or deleting the plugin preserves settings and security records so an administrator does not lose incident evidence. Site owners who want to remove that data can delete the All PHP, JavaScript and CSS source is included in this plugin package. The\nfiles in admin\/js\/ and admin\/css\/ are the actual readable source used by\nWordPress, including admin\/js\/deactivation.js, admin\/css\/deactivation.css\nand admin\/css\/toolbar.css. No compilation, minification, npm, Composer or\nother build step is required. Edit the bundled source files directly and\ntest on a development WordPress installation before distributing changes.\nThis package does not bundle compressed third-party JavaScript libraries.<\/p>\n\n Request-field inspection is capped at eight nested array levels, 256 visited entries across GET and POST, 4,000 bytes per value and 65,536 combined field-name\/value bytes. Field names longer than 128 bytes or combined paths longer than 256 bytes are skipped. The request URI has a separate 8,192-byte cap. Sensitive fields are excluded. Inputs beyond these inspection budgets are not examined; reaching a limit does not reject the request. These limits bound plugin inspection work, not PHP request parsing or all denial-of-service traffic.<\/p>\n\n\n For sites behind a trusted reverse proxy, define Quarantine is available only when No. A new installation starts in monitor mode. Blocking must be enabled deliberately by an administrator.<\/p><\/dd>\n No. This WordPress.org distribution runs locally and does not contact ZEISMO.<\/p><\/dd>\n No. A finding is a pattern match or an integrity change that needs review. Scan-limit and root traversal errors are reported. Unsupported file types, files over 2 MB, unreadable files and symbolic links are excluded; individual skipped files are not listed. Accepting an integrity baseline does not certify files as safe.<\/p><\/dd>\n No. The local controls in this WordPress.org edition work without a ZEISMO account, licence key or paid plan.<\/p><\/dd>\n No. This edition uses local request rules, file patterns and baseline comparisons. It does not send files to a cloud AI service or provide automatic malware cleanup. Review findings before taking action.<\/p><\/dd>\n No. It is a WordPress application-level tool. It does not filter traffic before it reaches your server, cover every attack or replace backups, updates and hosting-level protections.<\/p><\/dd>\n No. Settings and records are preserved to avoid destroying incident evidence. The Privacy and data handling section identifies the options and table prefix for administrators who decide to remove them manually.<\/p><\/dd>\n Yes, after a server administrator defines Privacy and data handling<\/h3>\n\n
zeismo_security_settings<\/code>, zeismo_sec_db_version<\/code>, zeismo_sec_setup_complete<\/code> and zeismo_sec_deactivation_feedback<\/code> options and the database tables whose names begin with their WordPress table prefix followed by zeismo_sec_<\/code>.<\/p>\n\nDevelopment and source code<\/h3>\n\n
Request inspection limits<\/h3>\n\n
\n
ZEISMO_SEC_TRUSTED_PROXIES<\/code> in wp-config.php<\/code> with the actual proxy IP addresses or CIDR ranges before selecting a forwarded-address mode.<\/p>\n\nZEISMO_SEC_QUARANTINE_DIR<\/code> points to an existing private writable directory outside all public document roots. Review findings and keep backups before moving files.<\/p>\n\n\n\n
Will ZEISMO Security block visitors immediately?<\/h3><\/dt>\n
Does the plugin send my files or traffic to ZEISMO?<\/h3><\/dt>\n
Is every scanner finding malware?<\/h3><\/dt>\n
Do I need an account or paid plan?<\/h3><\/dt>\n
Does this edition use cloud AI or automatically remove malware?<\/h3><\/dt>\n
Will it replace hosting security, backups or a network firewall?<\/h3><\/dt>\n
Does deleting the plugin delete security records?<\/h3><\/dt>\n
Can I use forwarded client IP headers?<\/h3><\/dt>\n
ZEISMO_SEC_TRUSTED_PROXIES<\/code>. Merely selecting a proxy mode does not trust arbitrary forwarded headers.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.0<\/h4>\n\n
\n