Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3616719,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3616719,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3616719,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3616719,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3616719,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250},"banner.svg":{"filename":"banner.svg","revision":3616719,"resolution":false,"location":"assets","locale":false}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3616719,"resolution":"1","location":"assets","locale":"","width":1852,"height":994},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3616719,"resolution":"2","location":"assets","locale":"","width":1852,"height":994},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3616719,"resolution":"3","location":"assets","locale":"","width":1852,"height":994},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3616719,"resolution":"4","location":"assets","locale":"","width":1852,"height":994},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3616719,"resolution":"5","location":"assets","locale":"","width":1852,"height":994},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3616719,"resolution":"6","location":"assets","locale":"","width":1852,"height":994},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3616719,"resolution":"7","location":"assets","locale":"","width":1852,"height":994},"screenshot-8.png":{"filename":"screenshot-8.png","revision":3616719,"resolution":"8","location":"assets","locale":"","width":1852,"height":994}},"screenshots":{"1":"Unified security dashboard \u2014 posture score, per-module status, live protection, and a prioritized action queue.","2":"Runtime firewall in block mode \u2014 blocked attacks grouped by rule, each with a plain-language \"why blocked\" explanation.","3":"Hardening audit \u2014 posture across configuration surfaces with AI-prioritized, step-by-step remediation guidance.","4":"Identity & access \u2014 privilege-drift detection, account posture (MFA, dormant admins), and live sessions and blocked IPs.","5":"File and code integrity \u2014 triage of integrity findings, including AI-analyzed malware-signature detection.","6":"Vulnerability scanner \u2014 installed plugins matched against the CVE feed, grouped per plugin with fix guidance.","7":"Findings \u2014 every finding across modules in one place, filterable by severity and module, with AI analysis.","8":"Audit log \u2014 tamper-evident activity trail of security-relevant events with user and IP attribution."}},"plugin_section":[],"plugin_tags":[2353,1174,1184,600,6460],"plugin_category":[54],"plugin_contributors":[79685],"plugin_business_model":[],"class_list":["post-313440","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-firewall","plugin_tags-malware","plugin_tags-security","plugin_tags-vulnerability","plugin_category-security-and-spam-protection","plugin_contributors-wisdmlabs","plugin_committers-wisdmlabs"],"banners":{"banner":"https:\/\/ps.w.org\/securyn\/assets\/banner-772x250.png?rev=3616719","banner_2x":"https:\/\/ps.w.org\/securyn\/assets\/banner-1544x500.png?rev=3616719","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/securyn\/assets\/icon.svg?rev=3616719","icon":"https:\/\/ps.w.org\/securyn\/assets\/icon.svg?rev=3616719","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/securyn\/assets\/screenshot-1.png?rev=3616719","caption":"Unified security dashboard \u2014 posture score, per-module status, live protection, and a prioritized action queue."},{"src":"https:\/\/ps.w.org\/securyn\/assets\/screenshot-2.png?rev=3616719","caption":"Runtime firewall in block mode \u2014 blocked attacks grouped by rule, each with a plain-language \"why blocked\" explanation."},{"src":"https:\/\/ps.w.org\/securyn\/assets\/screenshot-3.png?rev=3616719","caption":"Hardening audit \u2014 posture across configuration surfaces with AI-prioritized, step-by-step remediation guidance."},{"src":"https:\/\/ps.w.org\/securyn\/assets\/screenshot-4.png?rev=3616719","caption":"Identity & access \u2014 privilege-drift detection, account posture (MFA, dormant admins), and live sessions and blocked IPs."},{"src":"https:\/\/ps.w.org\/securyn\/assets\/screenshot-5.png?rev=3616719","caption":"File and code integrity \u2014 triage of integrity findings, including AI-analyzed malware-signature detection."},{"src":"https:\/\/ps.w.org\/securyn\/assets\/screenshot-6.png?rev=3616719","caption":"Vulnerability scanner \u2014 installed plugins matched against the CVE feed, grouped per plugin with fix guidance."},{"src":"https:\/\/ps.w.org\/securyn\/assets\/screenshot-7.png?rev=3616719","caption":"Findings \u2014 every finding across modules in one place, filterable by severity and module, with AI analysis."},{"src":"https:\/\/ps.w.org\/securyn\/assets\/screenshot-8.png?rev=3616719","caption":"Audit log \u2014 tamper-evident activity trail of security-relevant events with user and IP attribution."}],"raw_content":"\n
Most WordPress security plugins report a problem. They do not explain it. You get an alert that a file changed, a login failed, or a plugin is vulnerable. You do not get the reason, the risk, or the next step.<\/p>\n\n
Securyn is different. Securyn watches your site, finds the security problems, and explains each one in plain language. For each finding, Securyn tells you three things: what happened, why it is a risk, and the WordPress screen to open to correct it.<\/p>\n\n
Securyn is a detect-and-guide plugin. Securyn does not change your plugins, themes, core files, or configuration for you. You stay in control of every change. Securyn shows you the problem and the correct screen. You decide when to act.<\/p>\n\n
Securyn combines six security tools in one dashboard:<\/p>\n\n
Each finding includes a short, human-readable explanation. You do not need to be a developer to understand what happened or what to do next. Securyn writes the alert in plain English and links you to the correct WordPress screen, such as Plugins or Updates.<\/p>\n\n
AI narratives use a Bring-Your-Own-Key model. You supply your own key from OpenAI, Anthropic, or Google Gemini. No request goes through a Securyn server. If you add no key, every non-AI tool continues to work. Only the AI narratives and the AI triage turn off.<\/p>\n\n
This plugin connects to the following external services under specific conditions. No data is sent unless the described trigger occurs.<\/p>\n\n
The file-integrity module fetches official checksums and package metadata from WordPress.org to verify that core files, plugins, and themes have not been tampered with. Only the component slug and version are transmitted; no site or user data is sent.<\/p>\n\n
Data sent: WordPress version and locale (core checksums), plugin slug and version (plugin checksums), theme slug (theme info).\nWhen: during a file-integrity scan, or when a component is checked against its official checksums.<\/p>\n\n
The vulnerability module also queries api.wordpress.org\/plugins\/info\/1.2\/ (via the WordPress core plugins_api() function) to check whether each installed plugin slug is still listed in the official plugin directory. Only the plugin slug is transmitted.<\/p>\n\n
Data sent: plugin slug.\nWhen: on the scheduled vulnerability sync (every 4 days by default) and when manually triggered.<\/p>\n\n
The vulnerability scanner fetches CVE data from the Wordfence Intelligence v3 feed to check installed plugins and themes against known vulnerabilities. Requests are made on a scheduled basis (daily by default) and cached locally. A free Wordfence API key is required; you can obtain one at wordfence.com.<\/p>\n\n
Data sent: an HTTP GET request containing the plugin's user-agent string and the Wordfence API key (as a Bearer token in the Authorization header). No site URLs, user data, or other site-specific information is transmitted.\nWhen: on the scheduled vulnerability sync and when manually triggered from the Securyn dashboard.<\/p>\n\n
The vulnerability scanner queries the wpvulnerability.net API for CVE data. This is the default vulnerability source when no Wordfence API key is configured, and serves as a fallback if the Wordfence feed is unreachable.<\/p>\n\n
Data sent: plugin\/theme slug or WordPress version in the URL path. No site-specific or user-specific data is transmitted.\nWhen: during a scheduled or manual vulnerability sync, whenever wpvulnerability.net is the active source.<\/p>\n\n
Note: the project runs its API on the wpvulnerability.net domain (the endpoint this plugin queries), while its website, documentation, Terms of Use, and Privacy Policy are hosted on wpvulnerability.com.<\/p>\n\n
If you configure an OpenAI API key under Securyn > Settings, the plugin sends security finding summaries to the OpenAI API for AI-assisted narratives and triage.<\/p>\n\n
Data sent: security finding summaries (vulnerability descriptions, hardening check results). No credentials, user data, or site URLs are included in the payload.\nWhen: only when an API key is configured and a user views a finding detail or triggers AI triage.<\/p>\n\n
If you configure an Anthropic API key under Securyn > Settings, the plugin sends security finding summaries to the Anthropic API for AI-assisted narratives and triage.<\/p>\n\n
Data sent: security finding summaries (vulnerability descriptions, hardening check results). No credentials, user data, or site URLs are included in the payload.\nWhen: only when an API key is configured and a user views a finding detail or triggers AI triage.<\/p>\n\n
If you configure a Google Gemini API key under Securyn > Settings, the plugin sends security finding summaries to the Google Generative Language API for AI-assisted narratives and triage.<\/p>\n\n
Data sent: security finding summaries (vulnerability descriptions, hardening check results). No credentials, user data, or site URLs are included in the payload.\nWhen: only when an API key is configured and a user views a finding detail or triggers AI triage.<\/p>\n\n
On WordPress 7.0 and later, Securyn can delegate AI requests to the built-in WordPress AI Client via the Connectors API. The external provider contacted depends on the connector the site administrator has configured in WordPress settings. Securyn sends the same security finding summaries described above; no additional data is transmitted.<\/p>\n\n
When: only when WordPress 7.0+ is detected, the core AI Client connector is active, and no BYOK API key is configured for another provider.<\/p>\n\n
securyn<\/code> folder to the \/wp-content\/plugins\/<\/code> directory. Or install the plugin from the Plugins screen.<\/li>\n- Activate the plugin from the Plugins screen in WordPress.<\/li>\n
- Open the Securyn menu in the admin sidebar. Run the initial setup.<\/li>\n
- Optional: add your OpenAI, Anthropic, or Google Gemini API key under Securyn > Settings to turn on AI narratives.<\/li>\n<\/ol>\n\n\n
\nDoes Securyn fix hacked files automatically?<\/h3><\/dt>\nNo. Securyn does not change your files for you. Securyn shows you what changed and why it is a risk. Then Securyn links you to the correct WordPress screen, so you make the change yourself. You stay in control of every action.<\/p><\/dd>\n
What is the difference between Securyn and Wordfence?<\/h3><\/dt>\nWordfence and similar plugins report a problem, but they do not always explain it. Securyn explains each finding in plain language. Securyn tells you what happened, why it is a risk, and the exact screen to open to correct it. Securyn also combines a firewall, a vulnerability scanner, identity checks, file-integrity checks, hardening checks, and an audit log in one dashboard. Securyn can also use the Wordfence Intelligence v3 feed for vulnerability data when you add a free Wordfence key.<\/p><\/dd>\n
Do I need a developer to clean up a WordPress security problem?<\/h3><\/dt>\nNo. Securyn writes each alert in plain language. Securyn links you to the WordPress screen where you make the change, such as Plugins or Updates. You do not need to read technical logs or edit code to understand the problem.<\/p><\/dd>\n
Does Securyn need an API key?<\/h3><\/dt>\nNo. All non-AI tools work without a key. The AI narratives and the AI triage turn on only when you add a key.<\/p><\/dd>\n
Where does the vulnerability data come from?<\/h3><\/dt>\nSecuryn uses the wpvulnerability.net feed by default. If you add a free Wordfence API key, Securyn uses the Wordfence Intelligence v3 feed and keeps wpvulnerability.net as a fallback. Securyn caches the results on your site.<\/p><\/dd>\n
Can agencies use Securyn on many sites?<\/h3><\/dt>\nYes. Securyn works on any single WordPress site. An agency can install Securyn on each site it manages. Each site keeps its own findings, firewall rules, and audit log.<\/p><\/dd>\n
Does Securyn modify my plugins, themes, or core files?<\/h3><\/dt>\nNo. Securyn does not write to your plugins, themes, core files, or wp-config. When Securyn finds a problem, it links you to the correct WordPress screen \u2014 Plugins, Updates, or a settings page. You make the change and stay in control. Manual controls, such as ending a suspicious login session, act only when you start them.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.0<\/h4>\n\n
Initial release.<\/p>\n\n
\n- Runtime firewall with an OWASP Top 5 ruleset, rate limits, and an automatic blocklist.<\/li>\n
- Vulnerability scanner that checks installed plugins and themes against the wpvulnerability.net feed, with an optional Wordfence Intelligence v3 feed.<\/li>\n
- Identity module with login risk checks, session monitors, and privilege-drift alerts.<\/li>\n
- File-integrity baseline and drift detection, verified against official WordPress.org checksums.<\/li>\n
- Hardening checks with step-by-step guidance and an optional AI advisor.<\/li>\n
- Tamper-evident audit log with automatic retention cleanup.<\/li>\n
- Plain-language explanations for every finding, each linked to the correct WordPress screen.<\/li>\n
- Optional AI narratives with a Bring-Your-Own-Key model (OpenAI, Anthropic, or Google Gemini).<\/li>\n<\/ul>","raw_excerpt":"Securyn is a WordPress security operations plugin. It explains every finding in plain English and shows you where to fix it.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/313440","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=313440"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/wisdmlabs"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=313440"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=313440"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=313440"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=313440"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=313440"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=313440"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}