[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fU91v932-LjudTNo2vexjAiSdlfnSEZjTQPSCJmANGmA":3,"$fSwMdCCQzf2v-l_EgsAalcvFWXmuqBmU6wF2o8pjaseA":219,"$fZ45cXEpUlp8vrXaNEF4e-RA0ryTewSuCC4gzjFGw3g8":224},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"discovery_status":29,"vulnerabilities":30,"developer":31,"crawl_stats":27,"alternatives":37,"analysis":135,"fingerprints":189},"servicepress","ServicePress Connector Core","2.3.0","Harmedia Studios","https:\u002F\u002Fprofiles.wordpress.org\u002Fharmediastudios\u002F","\u003Cp>ServicePress Connector Core transforms WordPress into an enterprise operational integration edge for ServiceNow.\u003C\u002Fp>\n\u003Cp>Built for enterprise WordPress environments, ServicePress provides centralized operational visibility, inventory synchronization, event-driven workflows, multisite governance, and controlled integration patterns between WordPress and ServiceNow.\u003C\u002Fp>\n\u003Cp>ServicePress supports:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Single WordPress installations\u003C\u002Fli>\n\u003Cli>WordPress Multisite networks\u003C\u002Fli>\n\u003Cli>Large distributed WordPress environments\u003C\u002Fli>\n\u003Cli>Enterprise operational workflows\u003C\u002Fli>\n\u003Cli>Security and vulnerability visibility\u003C\u002Fli>\n\u003Cli>Controlled transport and synchronization pipelines\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Unlike earlier inventory-only integrations, ServicePress 2.0 introduces:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Controlled outbound transport architecture\u003C\u002Fli>\n\u003Cli>Queue-based synchronization workflows\u003C\u002Fli>\n\u003Cli>Enterprise multisite governance\u003C\u002Fli>\n\u003Cli>Scoped payload management\u003C\u002Fli>\n\u003Cli>Privacy and data filtering controls\u003C\u002Fli>\n\u003Cli>Role-aware administrative operations\u003C\u002Fli>\n\u003Cli>Diagnostic and operational tooling\u003C\u002Fli>\n\u003Cli>Optional ServiceNow pull API compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Version 2.3.0 Minor Update\u003C\u002Fh3>\n\u003Cp>ServicePress 2.3.0 is a minor update from ServicePress 2.2.0.\u003C\u002Fp>\n\u003Cp>This release preserves the existing ServicePress integration model while\u003Cbr \u002F>\nadding enterprise credential protection, authorization controls, transport\u003Cbr \u002F>\nsecurity, operational safeguards, and expanded administration capabilities.\u003C\u002Fp>\n\u003Cp>Highlights include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AES-256-GCM encrypted credential storage\u003C\u002Fli>\n\u003Cli>Automatic migration of existing ServicePress credentials\u003C\u002Fli>\n\u003Cli>Credential rotation, ownership, expiration, health, and audit metadata\u003C\u002Fli>\n\u003Cli>Administrative credential views that never redisplay stored secrets\u003C\u002Fli>\n\u003Cli>Dedicated least-privilege ServicePress capabilities\u003C\u002Fli>\n\u003Cli>Capability and nonce protection for state-changing actions\u003C\u002Fli>\n\u003Cli>Mandatory recursive secret redaction\u003C\u002Fli>\n\u003Cli>Mandatory omission of request and response bodies from persistent logs\u003C\u002Fli>\n\u003Cli>HTTPS-only ServiceNow transport validation\u003C\u002Fli>\n\u003Cli>ServiceNow hostname allowlisting\u003C\u002Fli>\n\u003Cli>Private, reserved, loopback, link-local, and metadata address rejection\u003C\u002Fli>\n\u003Cli>Mandatory TLS certificate verification\u003C\u002Fli>\n\u003Cli>Redirect prevention for credential-bearing outbound requests\u003C\u002Fli>\n\u003Cli>Queue and retry management\u003C\u002Fli>\n\u003Cli>Import Readiness validation\u003C\u002Fli>\n\u003Cli>Multisite diagnostics and governance improvements\u003C\u002Fli>\n\u003Cli>Secure-by-default ServiceNow Pull API controls\u003C\u002Fli>\n\u003Cli>Multisite-aware uninstall and data-retention handling\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Enterprise Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>WordPress multisite inventory synchronization\u003C\u002Fli>\n\u003Cli>Controlled ServiceNow integration workflows\u003C\u002Fli>\n\u003Cli>Queue-based payload processing\u003C\u002Fli>\n\u003Cli>Configurable transports and systems\u003C\u002Fli>\n\u003Cli>Payload inspection and previewing\u003C\u002Fli>\n\u003Cli>Event simulation and operational testing\u003C\u002Fli>\n\u003Cli>Privacy and data scope controls\u003C\u002Fli>\n\u003Cli>Multisite diagnostics and operational governance\u003C\u002Fli>\n\u003Cli>Optional \u003Ccode>\u002Fspnow\u002Fv1\u003C\u002Fcode> compatibility layer for ServiceNow pull integrations\u003C\u002Fli>\n\u003Cli>Application Passwords disabled by default\u003C\u002Fli>\n\u003Cli>Capability-protected administrative workflows\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>ServiceNow Integration\u003C\u002Fh3>\n\u003Cp>ServicePress integrates with certified ServiceNow applications and workflows to provide:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WordPress operational visibility\u003C\u002Fli>\n\u003Cli>Site inventory synchronization\u003C\u002Fli>\n\u003Cli>Plugin and theme visibility\u003C\u002Fli>\n\u003Cli>Event-driven operational workflows\u003C\u002Fli>\n\u003Cli>Vulnerability intelligence integrations\u003C\u002Fli>\n\u003Cli>Enterprise observability pipelines\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Additional ServicePress integrations may include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Wordfence\u003C\u002Fli>\n\u003Cli>WooCommerce\u003C\u002Fli>\n\u003Cli>LearnPress\u003C\u002Fli>\n\u003Cli>Enterprise publishing workflows\u003C\u002Fli>\n\u003Cli>Operational control extensions\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Security Model\u003C\u002Fh3>\n\u003Cp>ServicePress 2.0 introduces a significantly hardened architecture compared to earlier releases.\u003C\u002Fp>\n\u003Cp>Security improvements include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Capability-protected REST routes\u003C\u002Fli>\n\u003Cli>Controlled multisite context switching\u003C\u002Fli>\n\u003Cli>Optional legacy compatibility APIs\u003C\u002Fli>\n\u003Cli>Application Passwords disabled by default\u003C\u002Fli>\n\u003Cli>Request sanitization helpers\u003C\u002Fli>\n\u003Cli>Scoped payload controls\u003C\u002Fli>\n\u003Cli>Privacy-aware synchronization settings\u003C\u002Fli>\n\u003Cli>Queue isolation and controlled transport workflows\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Legacy compatibility APIs are disabled unless explicitly enabled for migration or integration compatibility purposes.\u003C\u002Fp>\n\u003Ch3>ServiceNow Pull API\u003C\u002Fh3>\n\u003Cp>ServicePress 2.0 optionally supports legacy \u003Ccode>\u002Fspnow\u002Fv1\u003C\u002Fcode> pull endpoints for backward compatibility with existing ServiceNow integrations.\u003C\u002Fp>\n\u003Cp>Supported compatibility routes include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>\u002Fspnow\u002Fv1\u002Fsites\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fspnow\u002Fv1\u002Fnetworks\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fspnow\u002Fv1\u002Fnetwork_info\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fspnow\u002Fv1\u002Fsite_settings\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>These routes are:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Capability protected\u003C\u002Fli>\n\u003Cli>Multisite aware\u003C\u002Fli>\n\u003Cli>Governed through the new 2.0 architecture\u003C\u002Fli>\n\u003Cli>Intended for migration and compatibility workflows\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Enterprise Multisite Safety\u003C\u002Fh3>\n\u003Cp>ServicePress 2.0 was designed specifically for enterprise and large multisite WordPress environments.\u003C\u002Fp>\n\u003Cp>The platform introduces controlled multisite context handling, scoped synchronization workflows, capability-protected administrative operations, and optional compatibility APIs designed to minimize operational risk in large distributed WordPress networks.\u003C\u002Fp>\n\u003Cp>ServicePress does not perform uncontrolled recursive synchronization or unmanaged background crawling across multisite environments.\u003C\u002Fp>\n\u003Ch3>Legal Disclosure\u003C\u002Fh3>\n\u003Cp>ServicePress facilitates operational integration workflows between WordPress and ServiceNow environments.\u003C\u002Fp>\n\u003Cp>Each organization is responsible for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The configuration of synchronization workflows\u003C\u002Fli>\n\u003Cli>Data governance and transport policies\u003C\u002Fli>\n\u003Cli>ServiceNow operational workflows\u003C\u002Fli>\n\u003Cli>WordPress administrative governance\u003C\u002Fli>\n\u003Cli>Compliance and operational review processes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>ServicePress stores configuration and operational records required to execute configured integration workflows. Data transmitted to external systems is limited by the configured synchronization, privacy, and data-scope controls.\u003C\u002Fp>\n\u003Ch3>External Links\u003C\u002Fh3>\n\u003Cp>ServicePress Website:\u003Cbr \u002F>\nhttps:\u002F\u002Fservicepress.app\u003C\u002Fp>\n\u003Cp>ServiceNow Store:\u003Cbr \u002F>\nhttps:\u002F\u002Fstore.servicenow.com\u002F\u003C\u002Fp>\n\u003Cp>Harmedia Studios:\u003Cbr \u002F>\nhttps:\u002F\u002Fharmediastudios.com\u003C\u002Fp>\n","Enterprise operational integration platform connecting WordPress and ServiceNow environments.",10,2703,0,"2026-07-21T18:57:00.000Z","7.0.2","6.0","8.0",[19,20,21,22,23],"automation","enterprise","multisite","security","servicenow","https:\u002F\u002Fservicepress.app","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.2.3.0.zip",100,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":32,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"harmediastudios",1,30,94,"2026-08-30T08:53:22.387Z",[38,59,80,99,116],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":26,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":57,"download_link":58,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"no-unsafe-inline","No unsafe-inline","1.3.0","Giuseppe","https:\u002F\u002Fprofiles.wordpress.org\u002Fmociofiletto\u002F","\u003Cp>Content Security Policy (CSP) is a computer security standard introduced to prevent cross-site scripting (XSS), clickjacking and other code injection attacks resulting from execution of malicious content in the trusted web page context.\u003Cbr \u002F>\nCross-site scripting (XSS) is a type of security vulnerability that can be found in some web applications.\u003Cbr \u002F>\nXSS attacks enable attackers to inject client-side scripts into web pages viewed by other users.\u003Cbr \u002F>\nA cross-site scripting vulnerability may be used by attackers to bypass access controls like the same-origin policy.\u003Cbr \u002F>\nLooking at National Vulnerability Database run by US NIST, \u003Cem>more than 1100 (November 2025) vulnerabilities\u003C\u002Fem> are reported as \u003Ca href=\"https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fsearch#\u002Fnvd\u002Fhome?vulnRevisionStatusList=published&keyword=XSS%20Wordpress&resultType=records\" rel=\"nofollow ugc\">XSS for WordPress’ plugins and themes\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cem>Keeping your site up-to-date\u003C\u002Fem> with the latest versions of plugins and themes is the \u003Cstrong>first\u003C\u002Fstrong> line of defense to ensure your site’s security.\u003C\u002Fp>\n\u003Cp>The second thing to do, is to \u003Cstrong>deploy a strict Content Security Policy\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch3>The main problem\u003C\u002Fh3>\n\u003Cp>The main problem with Content Security Policies implemented in the real world is that \u003Ca href=\"https:\u002F\u002Fresearch.google\u002Fpubs\u002Fpub45542\u002F\" rel=\"nofollow ugc\">they are too weak to really protect your site\u003C\u002Fa> and that many of them can be trivially bypassed by an attacker.\u003C\u002Fp>\n\u003Ch3>The proposed solution\u003C\u002Fh3>\n\u003Cp>Google researchers recommend, instead of whole host whitelisting, to activate individual scripts via a CSP nonces approach.\u003Cbr \u002F>\nIn addition, in order to facilitate the adoption of nonce-based CSP, they proposed the ’strict-dynamic’ keyword.\u003C\u002Fp>\n\u003Ch3>The problem(s) with CSP in WordPress\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\n\u003Cp>Manual creation of a policy\u003C\u002Fp>\n\u003Cp>Usually, a WordPress project is a mix of code written by different authors who contributed to the Core and or wrote plugins and themes.\u003Cbr \u002F>\nIf it is possible to whitelist every external script loaded from a \u003Ccode>\u003Cscript src=\"\">\u003C\u002Fcode>, the real truth is that in a WordPress project you can have dozens of those scripts included with your plugins and calculate a cryptographic hash for each of them to be included in your CSP header can be a frustrating job. However, there are many browser extensions and WordPress’ plugins that can help you in this job.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Inline scripts\u003C\u002Fp>\n\u003Cp>WordPress core, and plugins, use inline scripts. For these scripts, you can compute hashes to be inserted manually into your policy, only if these scripts do not change at any page load. Unfortunately, this is not very common, as it is frequent to include variable values calculated server side in inline scripts. And it means that your inline scripts change too frequently to manually add their hashes to your policy.\u003Cbr \u002F>\nThis commonly happens when scripts are \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FWordPress\u002FWordPress\u002Fblob\u002Fa793be201b9c23dbe8b90a6ecd53ab52336f0f91\u002Fwp-includes\u002Fscript-loader.php#L636\" rel=\"nofollow ugc\">“localized”\u003C\u002Fa>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>WordPress has no API to implement nonces for CSP\u003C\u002Fp>\n\u003Cp>Even if it is easy to generate a nonce for each page view, this nonce has to be inserted in every script tag used to embed inline scripts in your page as\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cscript nonce=\"rAnd0m\">\n    doWhatever();\n\u003C\u002Fscript>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>and in your script-src directive:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>script-src 'nonce-rAnd0m';\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>And, of course, a nonce must be unique for each HTTP response.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Unsafe hashes \u002F Inline styles\u003C\u002Fp>\n\u003Cp>Sometimes, HTML elements as images or buttons use HTML Event Attributes (onclick, onsubmit…) to let events trigger actions in a browser.\u003Cbr \u002F>\nYou cannot use hashes or nonces for script included in event attributes and, adopting a strict CSP, requires refactoring those patterns into safer alternatives or to use ‘unsafe-hashes’.\u003Cbr \u002F>\nYou got a similar problem when inline styles are used in HTML tags:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Ch1 style=\"color:blue;text-align:center;\">This is a heading\u003C\u002Fh1>\n\u003Cp style=\"color:red;\">This is a paragraph.\u003C\u002Fp>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>CSP Level 2 browsers may be ok with just putting the hash in your style-src directive. However, to allow hashes in the style attribute on inline CSS on browsers that support CSP Level 3, you may get an error like this\u003C\u002Fp>\n\u003Cpre>\u003Ccode>    Refused to apply inline style because it violates the following Content Security Policy directive: \"style-src 'self' 'sha256-nMxMqdZhkHxz5vAuW\u002FPAoLvECzzsmeAxD\u002FBNwG15HuA='\". Either the 'unsafe-inline' keyword, a hash ('sha256-nMxMqdZhkHxz5vAuW\u002FPAoLvECzzsmeAxD\u002FBNwG15HuA='), or a nonce ('nonce-...') is required to enable inline execution.\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>To allow inline styles you need to use ‘unsafe-hashes’ in your style-src directive (that is, in facts, unsafe).\u003Cbr \u002F>\n^\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>This plugin approach\u003C\u002Fh3>\n\u003Cp>This plugin affords those problems in this way:\u003C\u002Fp>\n\u003Col>\n\u003Cli>During a capture phase, it detects the scripts, styles and other embedded content present in the pages of your site and stores them in the database.\u003C\u002Fli>\n\u003Cli>Then you have to whitelist these contents from plugin admin.\u003C\u002Fli>\n\u003Cli>The plugin uses machine learning to cluster inline scripts trying to aggregate scripts generated by the same server side (PHP) code. So, you can authorize one script example to authorize all scripts that the classifier predicts to label as whitelisted clusters.\u003C\u002Fli>\n\u003Cli>You can choose to use hashes to authorize external scripts (and the plugin will allow you to include Subresource Integrity in your \u003Ccode>\u003Cscript>\u003C\u002Fcode> and \u003Ccode>\u003Clink>\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>You can use hashes or nonces to authorize inline scripts.\u003C\u002Fli>\n\u003Cli>You can ask the plugin to refactor your page to not use event attributes (converted in a inline script) and inline styles (converted in an internal CSS).\u003C\u002Fli>\n\u003Cli>You can set one or more violations’ report endpoints.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The plugin supports multisite installations and has (too) many options documented in inline help.\u003C\u002Fp>\n\u003Ch3>Creating a Content Security Policy\u003C\u002Fh3>\n\u003Cp>After plugin activation, go to Settings menu and search for CSP Settings submenu.\u003Cbr \u002F>\nThe steps you are supposed to do are the following.\u003C\u002Fp>\n\u003Col>\n\u003Cli>From the Tools tab, activate the capture of the tags and use your site by visiting all the pages or having your users visit them for a long time long period based on the use of your site (hours or days).\u003C\u002Fli>\n\u003Cli>From the Tools tab, perform the data clustering in the database (it can use many server resources).\u003C\u002Fli>\n\u003Cli>Go to the Base rules tab and include in the CSP directives the desired values ​​(help you with the table at the bottom of the page).\u003C\u002Fli>\n\u003Cli>Go to the external scripts tab, inline scripts tab and scripts invoked by event handlers tab and authorize the execution of all the legitimate scripts present on the pages of your site.\u003C\u002Fli>\n\u003Cli>Leaving the tag capture active, activate the policy test (at this stage the plugin will generate some violations of the temporary policy used to record additional values to be included in the directives of your “content security policy”).\u003C\u002Fli>\n\u003Cli>After visiting again your site pages, disable the capture of the tags and repeat the previous steps 2, 3 and 4.\u003C\u002Fli>\n\u003Cli>Enable site protection.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>N.B. When you update plugins or themes, if something doesn’t work properly on your site pages, temporarily deactivate the protection and repeat steps 1 to 7.\u003C\u002Fp>\n\u003Ch3>Plugin hooks\u003C\u002Fh3>\n\u003Ch4>Filters\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fpublic\u002Fclass-no-unsafe-inline-public.php#L419\" rel=\"nofollow ugc\">nunil_output_csp_headers_header_csp\u003C\u002Fa>\u003Cbr \u002F>\nnunil_output_csp_headers_header_csp is available since version 1.2.3 and can be used to modify the Content-Security-Policy header before it is sent to browser\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fsrc\u002FNunil_Manipulate_DOM.php#L930\" rel=\"nofollow ugc\">no_unsafe_inline_not_sri_sources\u003C\u002Fa>\u003Cbr \u002F>\nno_unsafe_inline_not_sri_sources can be used to modify the list of external resources that do not support SRI (Subresource Integrity)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fmu-plugin\u002Fno-unsafe-inline-output-buffering.php#L100\" rel=\"nofollow ugc\">no_unsafe_inline_final_output\u003C\u002Fa>\u003Cbr \u002F>\nno_unsafe_inline_final_output is an internal filter used to manipulate the output of the WordPress process just before the output is sent to the browser.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fmu-plugin\u002Fno-unsafe-inline-output-buffering.php#L107\" rel=\"nofollow ugc\">no_unsafe_inline_meta_injector\u003C\u002Fa>\u003Cbr \u002F>\nno_unsafe_inline_meta_injector is an internal filter hook used to inject meta http-equiv=”Content-Security-Policy” if variable is set\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Actions\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fincludes\u002Fclass-no-unsafe-inline.php#L213-L217\" rel=\"nofollow ugc\">nunil_upgrade\u003C\u002Fa> Functions hooked on nunil_upgrade will run when the plugin is upgraded\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fincludes\u002Fclass-no-unsafe-inline.php#L254\" rel=\"nofollow ugc\">nunil_output_csp_headers\u003C\u002Fa> Functions hooked to nunil_output_csp_headers will run when the plugin output the CSP HTTP response header\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Code and libraries\u003C\u002Fh3>\n\u003Cp>This version of the plugin uses:\u003Cbr \u002F>\n* to parse HTML:\u003Cbr \u002F>\n  * \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fivopetkov\u002Fhtml5-dom-document-php\" rel=\"nofollow ugc\">ivopetkov\u002FHTML5DOMDocument\u003C\u002Fa> on PHP\u003C8.4 and libxml\u003C=2.13.09\u003Cbr \u002F>\n  * \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMasterminds\u002Fhtml5-php\" rel=\"nofollow ugc\">Masterminds\\HTML5\u003C\u002Fa> on PHP\u003C8.4 and libxml>2.13.09\u003Cbr \u002F>\n  * \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fmigration84.new-features.php#migration84.new-features.dom\" rel=\"nofollow ugc\">\\Dom\\HTMLDocument\u003C\u002Fa>: The new ext-dom features with HTML5 support on PHP>8.4\u003Cbr \u002F>\n* \u003Ca href=\"https:\u002F\u002Frubixml.com\u002F\" rel=\"nofollow ugc\">RubixML\u003C\u002Fa> for machine learning \u003Cstrong>\u003Cem>from version 1.1.0\u003C\u002Fem>\u003C\u002Fstrong> – \u003Cem>\u003Ca href=\"https:\u002F\u002Fphp-ml.readthedocs.io\u002Fen\u002Flatest\u002F\" rel=\"nofollow ugc\">PHP-ML\u003C\u002Fa> was used in versions 1.0.x\u003C\u002Fem>;\u003Cbr \u002F>\n* \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fopctim\u002Fphp-nilsimsa\" rel=\"nofollow ugc\">opctim\u002Fphp-nilsimsa\u003C\u002Fa> to calculate and compare Nilsimsa digests.\u003C\u002Fp>\n\u003Cp>The log functions have been taken from\u003Cbr \u002F>\n* \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fperfectyorg\u002Fperfecty-push-wp\" rel=\"nofollow ugc\">perfectyorg\u002Fperfecty-push-wp\u003C\u002Fa>, \u003Cstrong>\u003Cem>something you should \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fperfecty-push-notifications\u002F\" rel=\"ugc\">really try\u003C\u002Fa> if you want to implement web Push notifications in your site.\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The \u003Cstrong>complete list of dependencies\u003C\u002Fstrong> used in this plugin can be seen in \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fnetwork\u002Fdependencies\" rel=\"nofollow ugc\">dependency graph\u003C\u002Fa> on GitHub.\u003C\u002Fp>\n\u003Ch3>Contributions, Issues, Bugs\u003C\u002Fh3>\n\u003Cp>Plugin code is hosted on a public repository on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa>.\u003Cbr \u002F>\nReach me over there to help and suggest.\u003C\u002Fp>\n","No unsafe-inline helps you to build a Content Security Policy avoiding to use 'unsafe-inline' and 'unsafe-hashes'.",200,11861,5,"2025-12-04T21:50:00.000Z","6.9.5","5.9","7.4",[54,55,21,22,56],"content-security-policy","csp","unsafe-inline","https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fno-unsafe-inline.1.3.0.zip",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":26,"downloaded":67,"rating":26,"num_ratings":68,"last_updated":69,"tested_up_to":15,"requires_at_least":70,"requires_php":71,"tags":72,"homepage":78,"download_link":79,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"24tt-document-verifier","24TT Document Verifier","2.2.0","24 Tech Time","https:\u002F\u002Fprofiles.wordpress.org\u002F24techtime\u002F","\u003Cp>The \u003Cstrong>24TT Document Verifier\u003C\u002Fstrong> is a powerful, enterprise-grade solution designed for institutions, universities, businesses, and government bodies globally to prove the authenticity of their issued documents.\u003C\u002Fp>\n\u003Cp>By embedding a secure verification portal directly into your WordPress website, you instantly protect your institution’s credibility and prevent the dissemination of counterfeit certificates, fake ID cards, and forged official letters.\u003C\u002Fp>\n\u003Ch3>🚀 What’s New in Version 2.2.0? (Expiration Engine & Future-Proofing)\u003C\u002Fh3>\n\u003Cp>Version 2.2.0 brings crucial compliance tools and prepares the plugin for an exciting future!\u003Cbr \u002F>\n* \u003Cstrong>Document Expiration Engine:\u003C\u002Fstrong> You can now set strict “Valid Until” \u002F Expiration dates for time-sensitive documents (like annual licenses, temporary IDs, or limited-term contracts).\u003Cbr \u002F>\n* \u003Cstrong>Bulk Upload Expiration Support:\u003C\u002Fstrong> The Bulk Add tool has been fully upgraded to allow mass-importing of expiration dates directly into your database.\u003Cbr \u002F>\n* \u003Cstrong>Opt-In & Upgrade Bridge:\u003C\u002Fstrong> We’ve integrated a secure, optional connectivity engine (powered by Freemius) to keep you updated on security patches and pave the way for upcoming premium features!\u003C\u002Fp>\n\u003Ch3>🎨 Version 2.1.0 Highlights (Branding & Data Integrity)\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Custom Branding Engine:\u003C\u002Fstrong> Match your institution’s exact brand colors using new intuitive color pickers for the frontend portal (Background, Button, and Hover states).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Duplicate Data Shield:\u003C\u002Fstrong> A strict new database constraint automatically prevents administrators from accidentally creating multiple documents with the exact same Verification ID via the standard editor or the Bulk Upload tool.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Legacy Duplicate Cleaner:\u003C\u002Fstrong> An automated background sweep that instantly detects and neutralizes any existing duplicate IDs in your database to protect systemic integrity.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>🌟 Version 2.0.0 Highlights (The Architecture Overhaul)\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>The “Kill Switch” (Global Settings):\u003C\u002Fstrong> Instant, granular control over your data. Easily toggle which document categories are accessible via the public search portal.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Native File Uploads:\u003C\u002Fstrong> Integrates directly with the native WordPress Media Library to visually upload and attach PDF or JPG files to any document record.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Dynamic UI Customizer:\u003C\u002Fstrong> Change the frontend search label instantly from the Settings dashboard.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The “Clean Workspace” Engine:\u003C\u002Fstrong> A premium admin dashboard that suppresses third-party marketing banners for a professional workspace.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Smart Front-End Rendering:\u003C\u002Fstrong> A modern success card that intelligently hides empty data fields for a flawless user presentation.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Core Features:\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Custom Verification Database:\u003C\u002Fstrong> Manage thousands of verifiable documents directly within a secure WordPress interface.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Comprehensive Data Fields:\u003C\u002Fstrong> Store exact details including Verification ID, Recipient Name, Grade\u002FPerformance, Issuing Authority, Expiration Dates, and PDF links.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Bulk Upload Tool:\u003C\u002Fstrong> Massively accelerate your workflow with dynamic, auto-expanding data rows.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Frontend Verification Portal:\u003C\u002Fstrong> Paste the \u003Ccode>[ttdvr_verify_document]\u003C\u002Fcode> shortcode on any page to deploy a beautiful, responsive search form.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Category Segmentation:\u003C\u002Fstrong> Organize records effortlessly using custom taxonomy tags.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Short Description\u003C\u002Fh3>\n\u003Cp>The ultimate enterprise-grade document verification system. Securely issue and verify certificates, ID cards, letters, and receipts directly on your WordPress website.\u003C\u002Fp>\n","The 24TT Document Verifier is a powerful, enterprise-grade solution designed for institutions, universities, businesses, and government bodies globall …",1736,4,"2026-05-28T08:20:00.000Z","5.8","",[73,74,75,76,77],"authenticity","certificate-validation","document-verification","enterprise-security","portal","https:\u002F\u002Fwordpress.24techtime.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002F24tt-document-verifier.2.2.0.zip",{"slug":81,"name":82,"version":83,"author":84,"author_profile":85,"description":86,"short_description":87,"active_installs":88,"downloaded":89,"rating":13,"num_ratings":13,"last_updated":90,"tested_up_to":91,"requires_at_least":16,"requires_php":17,"tags":92,"homepage":97,"download_link":98,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"r2k-captcha","R2K Security Captcha (for reCAPTCHA Enterprise & Cloudflare Turnstile)","1.0.3","systemsrtk","https:\u002F\u002Fprofiles.wordpress.org\u002Fsystemsrtk\u002F","\u003Cp>R2K Security Captcha is a comprehensive security plugin designed to safeguard your WordPress site’s critical entry points. By leveraging advanced captcha technology, it effectively blocks bots and malicious traffic without compromising user experience.\u003C\u002Fp>\n\u003Cp>Key features include:\u003Cbr \u002F>\n* \u003Cstrong>Dual-Service Support:\u003C\u002Fstrong> Seamlessly integrate with either \u003Cstrong>Google reCAPTCHA Enterprise\u003C\u002Fstrong> or \u003Cstrong>Cloudflare Turnstile\u003C\u002Fstrong>.\u003Cbr \u002F>\n* \u003Cstrong>Smart Protection:\u003C\u002Fstrong> Use reCAPTCHA Enterprise’s score-based system to dynamically assess risk and block suspicious activity.\u003Cbr \u002F>\n* \u003Cstrong>User-Friendly Turnstile:\u003C\u002Fstrong> Implement a non-intrusive, privacy-first security solution with Cloudflare Turnstile.\u003Cbr \u002F>\n* \u003Cstrong>Advanced Form Protection:\u003C\u002Fstrong> Secure your \u003Cstrong>login\u003C\u002Fstrong>, \u003Cstrong>registration\u003C\u002Fstrong>, and \u003Cstrong>lost password\u003C\u002Fstrong> forms.\u003Cbr \u002F>\n* \u003Cstrong>IP Whitelisting:\u003C\u002Fstrong> Easily add trusted IP addresses to a whitelist to bypass captcha checks for specific users or locations.\u003Cbr \u002F>\n* \u003Cstrong>Error Notifications:\u003C\u002Fstrong> Receive email notifications if your captcha keys fail, ensuring you are always aware of your site’s security status.\u003C\u002Fp>\n\u003Cp>This plugin provides a robust and secure layer of defense, making your website a safer place for real users while frustrating spammers and bots.\u003C\u002Fp>\n","Protect your WordPress website from spam and abuse with R2K Security Captcha. This plugin offers powerful security by integrating with two of the most …",60,458,"2025-12-16T09:24:00.000Z","6.8.6",[93,94,95,96,22],"captcha","recaptcha","recaptcha-enterprise","secure","https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fr2k-security-captcha","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fr2k-captcha.1.0.3.zip",{"slug":100,"name":101,"version":102,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":88,"downloaded":107,"rating":13,"num_ratings":13,"last_updated":108,"tested_up_to":50,"requires_at_least":109,"requires_php":110,"tags":111,"homepage":71,"download_link":115,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"weglob-auto-repair-for-wordfence-security","Weglob Auto Repair for Wordfence Security","1.0.0","weglob","https:\u002F\u002Fprofiles.wordpress.org\u002Fweglob\u002F","\u003Cp>Weglob Auto Repair for Wordfence Security is a WordPress plugin that connects to Wordfence Security and helps automate follow-up actions after a scan.\u003C\u002Fp>\n\u003Cp>You can configure the plugin to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>run on a schedule\u003C\u002Fli>\n\u003Cli>repair supported files automatically\u003C\u002Fli>\n\u003Cli>delete unknown or malicious files when you explicitly enable deletion\u003C\u002Fli>\n\u003Cli>keep detailed logs of each action\u003C\u002Fli>\n\u003Cli>send email notifications after runs\u003C\u002Fli>\n\u003Cli>exclude custom files and paths from automation\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The plugin is intended for site owners who already use Wordfence Security and want a controlled workflow for repetitive cleanup tasks.\u003C\u002Fp>\n","Automatically repairs or deletes files flagged by Wordfence Security on a configurable schedule.",280,"2026-04-09T22:48:00.000Z","5.0","7.2",[19,112,113,22,114],"maintenance","malware","wordfence","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fweglob-auto-repair-for-wordfence-security.1.0.0.zip",{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":11,"downloaded":124,"rating":13,"num_ratings":13,"last_updated":125,"tested_up_to":91,"requires_at_least":126,"requires_php":127,"tags":128,"homepage":132,"download_link":133,"security_score":134,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"content-sync-assistant","Content Sync Assistant","1.0.2","wowown","https:\u002F\u002Fprofiles.wordpress.org\u002Fwowown\u002F","\u003Cp>\u003Cstrong>EN:\u003C\u002Fstrong>\u003Cbr \u002F>\nContent Sync Assistant is a powerful WordPress plugin designed to help users easily synchronize posts, pages, and other content across multiple WordPress sites. Whether you’re a business managing multiple websites or a blogger needing to share content across sites, this plugin can significantly improve your work efficiency.\u003C\u002Fp>\n\u003Cp>Key Features (Extracted from plugin website):\u003Cbr \u002F>\n* Effortless Content Synchronization: Easily synchronize posts and pages across multiple WordPress sites.\u003Cbr \u002F>\n* Comprehensive Data Transfer: Supports the synchronization of categories, tags, featured images, and other crucial metadata.\u003Cbr \u002F>\n* Automatic synchronization: Automatic synchronization can be set to automatically synchronize to the target site when the source site content is updated.\u003Cbr \u002F>\n* Manual synchronization: Flexible manual synchronization options allow users to select specific content to synchronize.\u003Cbr \u002F>\n* Detailed Logging: Keep track of synchronization activities with comprehensive logs for easy monitoring and troubleshooting.\u003Cbr \u002F>\n* User-Friendly Interface: An intuitive and easy-to-navigate interface makes content synchronization a breeze.\u003C\u002Fp>\n\u003Cp>For more detailed information and advanced features, please visit the plugin homepage: https:\u002F\u002Fwww.wowown.com\u003C\u002Fp>\n\u003Cp>\u003Cstrong>ZH:\u003C\u002Fstrong>\u003Cbr \u002F>\n内容同步助手是一款强大的WordPress插件，旨在帮助用户在多个WordPress站点之间轻松同步文章、页面等内容。无论您是管理多个网站的企业，还是需要跨站点共享内容的博主，这款插件都能显著提升您的工作效率。\u003C\u002Fp>\n\u003Cp>主要功能（从插件网站提取）：\u003Cbr \u002F>\n* 轻松的内容同步：轻松地在多个 WordPress 站点之间同步文章和页面。\u003Cbr \u002F>\n* 全面的数据传输：支持同步分类、标签、特色图像和其他关键元数据。\u003Cbr \u002F>\n* 自动同步：可设置自动同步，当源站点内容更新时，自动同步到目标站点。\u003Cbr \u002F>\n* 手动同步： 灵活的手动同步选项，允许用户选择要同步的特定内容。\u003Cbr \u002F>\n* 详细日志记录：通过全面的日志跟踪同步活动，方便监控和故障排除。\u003Cbr \u002F>\n* 用户友好的界面：直观且易于导航的界面使内容同步变得轻而易举。\u003C\u002Fp>\n\u003Cp>有关更详细的信息和高级功能，请访问插件主页：https:\u002F\u002Fwww.wowown.com\u002Fcontent-sync-assistant\u002F\u003C\u002Fp>\n","EN: Efficiently and reliably synchronize content between multiple WordPress sites. ZH: 高效可靠地在多个 WordPress 站点之间同步内容。",789,"2025-06-23T18:50:00.000Z","5.6","7.0",[19,129,21,130,131],"metadata","posts","synchronize","https:\u002F\u002Fwww.wowown.com\u002Fcontent-sync-assistant\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-sync-assistant.1.0.2.zip",92,{"attackSurface":136,"codeSignals":172,"taintFlows":180,"riskAssessment":181,"analyzedAt":188},{"hooks":137,"ajaxHandlers":168,"restRoutes":169,"shortcodes":170,"cronEvents":171,"entryPointCount":13,"unprotectedCount":13},[138,144,149,152,155,158,162,165],{"type":139,"name":140,"callback":141,"file":142,"line":143},"filter","wp_is_application_passwords_available","__return_true","core\\spnow_filter_application_password.php",11,{"type":145,"name":146,"callback":147,"file":148,"line":143},"action","rest_api_init","spnow_register_networks","core\\spnow_register_networks.php",{"type":145,"name":146,"callback":150,"file":148,"line":151},"spnow_register_network_info",51,{"type":145,"name":146,"callback":153,"file":154,"line":143},"spnow_register_rest_pre_callback","core\\spnow_register_sites.php",{"type":145,"name":146,"callback":156,"file":154,"line":157},"spnow_register_network_blogs",53,{"type":145,"name":146,"callback":159,"file":160,"line":161},"spnow_register_rest_servicepress_version_check","core\\spnow_register_site_version.php",12,{"type":145,"name":146,"callback":163,"file":164,"line":143},"spnow_register_rest_user_email","core\\spnow_register_user_email.php",{"type":145,"name":146,"callback":166,"file":167,"line":143},"spnow_register_user_roles","core\\spnow_register_user_roles.php",[],[],[],[],{"dangerousFunctions":173,"sqlUsage":174,"outputEscaping":176,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":179},[],{"prepared":33,"raw":13,"locations":175},[],{"escaped":177,"rawEcho":13,"locations":178},2,[],[],[],{"summary":182,"deductions":183},"Based on the provided static analysis and vulnerability history, the ServicePress plugin version 1.4 exhibits a strong security posture. The absence of identified vulnerabilities in its history, coupled with static analysis revealing no dangerous functions, no raw SQL queries, and all outputs being properly escaped, indicates good development practices. The plugin also has a minimal attack surface with zero entry points identified, and importantly, no taint flows were detected, suggesting a lack of paths for malicious data to be processed without proper sanitization.\n\nWhile the plugin demonstrates robust security for its current state and history, the lack of capability checks and nonce checks on entry points, if any were present (though the analysis shows none), could represent a potential concern if the attack surface were to expand in future versions. However, as the current attack surface is zero, this is a theoretical concern rather than an immediate risk. The overall impression is of a well-secured plugin, with no immediate exploitable vulnerabilities or historical patterns suggesting systemic issues.",[184,186],{"reason":185,"points":48},"No capability checks on entry points",{"reason":187,"points":48},"No nonce checks on entry points","2026-03-16T23:01:45.206Z",{"wat":190,"direct":197},{"assetPaths":191,"generatorPatterns":194,"scriptPaths":195,"versionParams":196},[192,193],"\u002Fwp-content\u002Fplugins\u002Fservicepress\u002Fcore\u002Fjs\u002Fspnow.js","\u002Fwp-content\u002Fplugins\u002Fservicepress\u002Fcore\u002Fcss\u002Fspnow.css",[],[192],[],{"cssClasses":198,"htmlComments":199,"htmlAttributes":202,"restEndpoints":203,"jsGlobals":207,"shortcodeOutput":218},[],[200,201,200],"\u003C!-- Register API Init - Register REST Route - Network Sites -->","\u003C!-- Register API Init - REST Pre Callback -->",[],[204,205,206],"\u002Fwp-json\u002Fspnow\u002Fv1\u002Fnetworks","\u002Fwp-json\u002Fspnow\u002Fv1\u002Fnetwork_info","\u002Fwp-json\u002Fspnow\u002Fv1\u002Fsites",[208,209,210,211,212,213,214,215,216,217],"SPNOW_SERVICENOW_CITY","SPNOW_SERVICENOW_VERSION","SPNOW_SERVICEPRESS_BUILD","SPNOW_SERVICEPRESS_VERSION","SPNOW_SERVICEPRESS_REST_BASE","SPNOW_SERVICEPRESS_API_VERSION","SPNOW_SERVICEPRESS_SLUG","SPNOW_SERVICEPRESS_PLUGIN_PATH","SPNOW_SERVICEPRESS_PLUGIN_URL","SPNOW_SERVICEPRESS_CORE_PATH",[],{"error":220,"url":221,"statusCode":222,"statusMessage":223,"message":223},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fservicepress\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":225,"versions":226},17,[227,233,239,246,253,260,267,274,281,288,295,302,309,316,323,329,336],{"version":6,"download_url":25,"svn_tag_url":228,"released_at":27,"has_diff":229,"diff_files_changed":230,"diff_lines":27,"trac_diff_url":231,"vulnerabilities":232,"is_current":220},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F2.3.0\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F2.2.0&new_path=%2Fservicepress%2Ftags%2F2.3.0",[],{"version":62,"download_url":234,"svn_tag_url":235,"released_at":27,"has_diff":229,"diff_files_changed":236,"diff_lines":27,"trac_diff_url":237,"vulnerabilities":238,"is_current":229},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.2.2.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F2.2.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F2.1.1&new_path=%2Fservicepress%2Ftags%2F2.2.0",[],{"version":240,"download_url":241,"svn_tag_url":242,"released_at":27,"has_diff":229,"diff_files_changed":243,"diff_lines":27,"trac_diff_url":244,"vulnerabilities":245,"is_current":229},"2.1.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.2.1.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F2.1.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F2.1.0&new_path=%2Fservicepress%2Ftags%2F2.1.1",[],{"version":247,"download_url":248,"svn_tag_url":249,"released_at":27,"has_diff":229,"diff_files_changed":250,"diff_lines":27,"trac_diff_url":251,"vulnerabilities":252,"is_current":229},"2.1.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.2.1.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F2.1.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F2.0.1&new_path=%2Fservicepress%2Ftags%2F2.1.0",[],{"version":254,"download_url":255,"svn_tag_url":256,"released_at":27,"has_diff":229,"diff_files_changed":257,"diff_lines":27,"trac_diff_url":258,"vulnerabilities":259,"is_current":229},"2.0.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.2.0.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F2.0.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F2.0.0&new_path=%2Fservicepress%2Ftags%2F2.0.1",[],{"version":261,"download_url":262,"svn_tag_url":263,"released_at":27,"has_diff":229,"diff_files_changed":264,"diff_lines":27,"trac_diff_url":265,"vulnerabilities":266,"is_current":229},"2.0.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.2.0.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F2.0.0\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F1.4&new_path=%2Fservicepress%2Ftags%2F2.0.0",[],{"version":268,"download_url":269,"svn_tag_url":270,"released_at":27,"has_diff":229,"diff_files_changed":271,"diff_lines":27,"trac_diff_url":272,"vulnerabilities":273,"is_current":229},"1.4","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.1.4.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F1.4\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F1.3&new_path=%2Fservicepress%2Ftags%2F1.4",[],{"version":275,"download_url":276,"svn_tag_url":277,"released_at":27,"has_diff":229,"diff_files_changed":278,"diff_lines":27,"trac_diff_url":279,"vulnerabilities":280,"is_current":229},"1.3","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.1.3.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F1.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F1.1.5&new_path=%2Fservicepress%2Ftags%2F1.3",[],{"version":282,"download_url":283,"svn_tag_url":284,"released_at":27,"has_diff":229,"diff_files_changed":285,"diff_lines":27,"trac_diff_url":286,"vulnerabilities":287,"is_current":229},"1.1.5","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.1.1.5.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F1.1.5\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F1.1.4&new_path=%2Fservicepress%2Ftags%2F1.1.5",[],{"version":289,"download_url":290,"svn_tag_url":291,"released_at":27,"has_diff":229,"diff_files_changed":292,"diff_lines":27,"trac_diff_url":293,"vulnerabilities":294,"is_current":229},"1.1.4","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.1.1.4.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F1.1.4\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F1.1.3&new_path=%2Fservicepress%2Ftags%2F1.1.4",[],{"version":296,"download_url":297,"svn_tag_url":298,"released_at":27,"has_diff":229,"diff_files_changed":299,"diff_lines":27,"trac_diff_url":300,"vulnerabilities":301,"is_current":229},"1.1.3","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.1.1.3.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F1.1.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F1.1.2&new_path=%2Fservicepress%2Ftags%2F1.1.3",[],{"version":303,"download_url":304,"svn_tag_url":305,"released_at":27,"has_diff":229,"diff_files_changed":306,"diff_lines":27,"trac_diff_url":307,"vulnerabilities":308,"is_current":229},"1.1.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.1.1.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F1.1.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F1.1.1&new_path=%2Fservicepress%2Ftags%2F1.1.2",[],{"version":310,"download_url":311,"svn_tag_url":312,"released_at":27,"has_diff":229,"diff_files_changed":313,"diff_lines":27,"trac_diff_url":314,"vulnerabilities":315,"is_current":229},"1.1.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.1.1.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F1.1.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F1.1&new_path=%2Fservicepress%2Ftags%2F1.1.1",[],{"version":317,"download_url":318,"svn_tag_url":319,"released_at":27,"has_diff":229,"diff_files_changed":320,"diff_lines":27,"trac_diff_url":321,"vulnerabilities":322,"is_current":229},"1.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.1.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F1.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F1.0.2&new_path=%2Fservicepress%2Ftags%2F1.1",[],{"version":119,"download_url":324,"svn_tag_url":325,"released_at":27,"has_diff":229,"diff_files_changed":326,"diff_lines":27,"trac_diff_url":327,"vulnerabilities":328,"is_current":229},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.1.0.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F1.0.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F1.0.1&new_path=%2Fservicepress%2Ftags%2F1.0.2",[],{"version":330,"download_url":331,"svn_tag_url":332,"released_at":27,"has_diff":229,"diff_files_changed":333,"diff_lines":27,"trac_diff_url":334,"vulnerabilities":335,"is_current":229},"1.0.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.1.0.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F1.0.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fservicepress%2Ftags%2F1.0.0&new_path=%2Fservicepress%2Ftags%2F1.0.1",[],{"version":102,"download_url":337,"svn_tag_url":338,"released_at":27,"has_diff":229,"diff_files_changed":339,"diff_lines":27,"trac_diff_url":27,"vulnerabilities":340,"is_current":229},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fservicepress.1.0.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fservicepress\u002Ftags\u002F1.0.0\u002F",[],[]]