Critical stability fixes: prevents admin lockout from firewall, reduces SIEM request timeouts, fixes uninstall leaving broken .htaccess, and expands REST API compatibility with popular plugins.<\/p>","1.2.2":"
Fixes bidirectional auto-update sync with the SIEM: corrects authentication headers, dedup hashing, version tracking, and update trigger logic.<\/p>","1.2.1":"
Maintenance release with Plugin Check compatibility fixes.<\/p>","1.2.0":"
Fixes login URL validation and cron cleanup on disconnect.<\/p>","1.1.9":"
Whitelist IPs are now sent to the SIEM during pairing to prevent them from being lost on sync.<\/p>","1.1.8":"
Nginx warning now shows only once and includes a link to the solution documentation.<\/p>","1.1.7":"
Deactivation now fully clears all cron jobs and .htaccess markers, including events re-scheduled by alert hooks.<\/p>","1.1.5":"
Fixes a multisite uninstall query edge case that could log an SQL warning.<\/p>","1.1.4":"
Uninstall cleanup now removes Vulnity firewall\/log folders recursively so nothing is left behind.<\/p>","1.1.3":"
Improved uninstall cleanup for firewall\/log folders in restrictive hosting environments.<\/p>","1.1.2":"
New rotating Vulnity logs plus safer firewall storage warnings and cleanup behavior for shared hosting.<\/p>","1.1.1":"
Conservative Stability and compatibility update focused on safer lifecycle handling and cleaner admin UX.<\/p>","1.0.5":" Version bump to 1.0.5.<\/p>","1.0.4":" Version bump to 1.0.4.<\/p>","1.0.3":" Compliance-focused update to align asset loading, documentation, and escaping with WordPress.org guidelines.<\/p>","1.0.2":" Initial public release featuring Vulnity SIEM integration and security monitoring dashboard.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3497049,"resolution":"128x128","location":"assets","locale":""},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3497049,"resolution":"256x256","location":"assets","locale":""}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3448570,"resolution":"1544x500","location":"assets","locale":""},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3448566,"resolution":"772x250","location":"assets","locale":""}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.5","1.1.7","1.1.8","1.1.9","1.2.0","1.2.1","1.2.2","1.2.3"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3460705,"resolution":"1","location":"assets","locale":""},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3460705,"resolution":"2","location":"assets","locale":""},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3460705,"resolution":"3","location":"assets","locale":""},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3460705,"resolution":"4","location":"assets","locale":""},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3460705,"resolution":"5","location":"assets","locale":""},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3460705,"resolution":"6","location":"assets","locale":""}},"screenshots":{"1":"Dashboard overview with real-time threat summary.","2":"Alert detail screen showing remediation steps.","3":"Settings page for configuring API credentials and scan schedules."},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[44486,5603,600,254825],"plugin_category":[54],"plugin_contributors":[254826],"plugin_business_model":[],"class_list":["post-259735","plugin","type-plugin","status-publish","hentry","plugin_tags-intrusion-detection","plugin_tags-monitoring","plugin_tags-security","plugin_tags-siem","plugin_category-security-and-spam-protection","plugin_contributors-manuelgalan","plugin_committers-manuelgalan"],"banners":{"banner":"https:\/\/ps.w.org\/vulnity\/assets\/banner-772x250.png?rev=3448566","banner_2x":"https:\/\/ps.w.org\/vulnity\/assets\/banner-1544x500.png?rev=3448570","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/vulnity\/assets\/icon-128x128.png?rev=3497049","icon_2x":"https:\/\/ps.w.org\/vulnity\/assets\/icon-256x256.png?rev=3497049","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/vulnity\/assets\/screenshot-1.png?rev=3460705","caption":"Dashboard overview with real-time threat summary."},{"src":"https:\/\/ps.w.org\/vulnity\/assets\/screenshot-2.png?rev=3460705","caption":"Alert detail screen showing remediation steps."},{"src":"https:\/\/ps.w.org\/vulnity\/assets\/screenshot-3.png?rev=3460705","caption":"Settings page for configuring API credentials and scan schedules."},{"src":"https:\/\/ps.w.org\/vulnity\/assets\/screenshot-4.png?rev=3460705","caption":""},{"src":"https:\/\/ps.w.org\/vulnity\/assets\/screenshot-5.png?rev=3460705","caption":""},{"src":"https:\/\/ps.w.org\/vulnity\/assets\/screenshot-6.png?rev=3460705","caption":""}],"raw_content":"\n Vulnity Security brings enterprise-grade threat detection to WordPress. It connects your site to Vulnity's SIEM platform, correlates events, and alerts you before issues become incidents.<\/p>\n\n To receive alerts, configure an API token and endpoint URL provided by your Vulnity SIEM account. Detailed configuration instructions are displayed after activating the plugin under Vulnity > Settings<\/strong>.<\/p>\n\n This plugin connects to Vulnity's external API hosted on Supabase Edge Functions (domain: This plugin is licensed under the GNU General Public License v2.0 or later. You are free to redistribute and\/or modify it under the terms of the GPL as published by the Free Software Foundation. The complete license text is included in the bundled Yes. The plugin requires an active Vulnity SIEM account to collect and analyze events.<\/p><\/dd>\n No. Event collection runs asynchronously and offloads processing to the Vulnity cloud platform.<\/p><\/dd>\n Absolutely. Use the Alert Policies<\/strong> section within the plugin settings to mute or reclassify events.<\/p><\/dd>\n\n<\/dl>\n\n\n.htaccess<\/code> cleanup update: Vulnity now removes only its own marker blocks on deactivation and leaves user rules untouched.<\/p>","1.1.0":"Features<\/h4>\n\n
\n
Integration Requirements<\/h4>\n\n
External Services<\/h4>\n\n
euxnoekqasvzwfcbybkg.supabase.co<\/code>, base URL https:\/\/euxnoekqasvzwfcbybkg.supabase.co\/functions\/v1<\/code>) to power SIEM alerts, inventory sync, and mitigation updates.<\/p>\n\n\n
\n
\n
\/pair-plugin<\/code>, \/unpair-plugin<\/code> (pairing and disconnecting the site).<\/li>\n\/heartbeat<\/code> (periodic health check).<\/li>\n\/connection-test<\/code> (manual connection test).<\/li>\n\/scan-site-info<\/code> (inventory sync).<\/li>\n\/generic-alert<\/code>, \/brute-force-alert<\/code>, \/file-security-alert<\/code>, \/manage-user<\/code>, \/user-management-alert<\/code>, \/permission-change-alert<\/code>, \/file-editor-alert<\/code>, \/plugin-change-alert<\/code>, \/theme-change-alert<\/code>, \/core-update-alert<\/code>, \/suspicious-query-alert<\/code>, \/scanner-detected-alert<\/code> (security alerts).<\/li>\n\/mitigation-config<\/code>, \/mitigation-update<\/code> (mitigation policy sync and block\/unblock updates).<\/li>\n<\/ul><\/li>\n\n
\n
License<\/h3>\n\n
license.txt<\/code> file and is also available online at https:\/\/www.gnu.org\/licenses\/gpl-2.0.html.<\/p>\n\n\n\n
\/wp-content\/plugins\/vulnity<\/code> directory or install from the WordPress plugin repository.<\/li>\n\n
Do I need a Vulnity SIEM subscription?<\/h3><\/dt>\n
Will the plugin slow down my site?<\/h3><\/dt>\n
Can I disable certain alerts?<\/h3><\/dt>\n
1.2.3<\/h4>\n\n
\n
Options -Indexes<\/code> to Protect Common Paths .htaccess rules as defense-in-depth measure.<\/li>\n1.2.2<\/h4>\n\n
\n
\/real-time-alerts<\/code> endpoint (now uses HMAC-SHA256 signature instead of token).<\/li>\nremediation<\/code> field in auto-update state events sent to the SIEM.<\/li>\nversion_old<\/code> not captured in auto-update events; now recorded via upgrader_pre_install<\/code> hook before files are replaced.<\/li>\ninstanceof WP_Automatic_Updater<\/code> instead of wp_doing_cron()<\/code> for broader compatibility.<\/li>\n.<\/code> (e.g. hello-dolly) in update event payloads.<\/li>\ntriggered_by<\/code> field to update events: siem_manual<\/code>, siem_auto_update<\/code>, or wp_auto_updater<\/code>.<\/li>\nparse_url()<\/code> with wp_parse_url()<\/code> for WordPress coding standards compliance.<\/li>\n<\/ul>\n\n1.2.1<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
wp_unschedule_hook()<\/code> for complete removal.<\/li>\n1.1.9<\/h4>\n\n
\n
1.1.8<\/h4>\n\n
\n
1.1.7<\/h4>\n\n
\n
final_deactivation_cleanup<\/code> at priority 9999 to ensure complete cron and .htaccess cleanup after all hooks fire.<\/li>\nwp_clear_scheduled_hook<\/code> with wp_unschedule_hook<\/code> to clear single events with arguments.<\/li>\nis_writable()<\/code> with vulnity_path_is_writable()<\/code> and WP_Filesystem_Direct<\/code>.<\/li>\n<\/ul>\n\n1.1.5<\/h4>\n\n
\n
sitemeta<\/code> table is not available to prevent SQL warnings in debug.log.<\/li>\n<\/ul>\n\n1.1.4<\/h4>\n\n
\n
1.1.3<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
.htaccess<\/code> without modifying user-defined rules.<\/li>\n1.1.0<\/h4>\n\n
\n
1.0.5<\/h4>\n\n
\n
1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n