Sucuri Security vulnerability records, audit logs and alert settings
Sucuri's listing for this plugin names security activity auditing, security hardening and customisable security alerts among its features.
Match the installed version to each record here, then read where its logs go, what has been hardened and who receives its alerts.
On this page
Sucuri Security vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 1 record for Sucuri Security. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 1.8.34
Worked out from data retrieved on .
Every affected range listed in this source for Sucuri Security ends before version 1.8.34.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Sucuri Security <= 1.8.33 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- High (CVSS 8.8)
- CVE:
- CVE-2022-29489
Affected versions- All versions up to and including 1.8.33
Patched versions: 1.8.34
Update to at least version 1.8.34.
Check Sucuri Security on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
What Sucuri Security is and where it takes input
The plugin's readme calls it "a security toolset for security integrity monitoring, malware detection and security hardening".
The installation steps on its WordPress.org listing mention a settings page for options "including the security alerts, hardening options, file system scanner paths and API service communication". WordPress's roles page says an Administrator has access to all administration features within a single site. Start by noting who holds that role.
Its log takes input from other people too: the vendor's article on email alerts lists "User fails to authenticate" and "File is uploaded" among the events the plugin logs.
Sucuri Security vulnerabilities by version: reading CVE-2022-29489
The history on this page shows the records the source data files under the slug sucuri-scanner.
Take CVE-2022-29489. Its title is "Sucuri Security <= 1.8.33 - Cross-Site Request Forgery", its affected range is all versions up to and including 1.8.33, and its patched versions field lists 1.8.34. Compare the installed version with that range, and with every other range the history shows on the day you read it.
Whatever the history holds, it describes versions, not how Sucuri Security is set up on a given site.
Where each Sucuri Security setting is read, and what to write down
Each check is done by reading, on a site you are authorised to review.
The vendor's knowledge base articles cited here are dated 27 March 2019, and where their screen names differ from the listing's, both are given.
The changelog on the listing words some entries as security changes, among them "Strengthen input validation, access checks, and output escaping", so read it as a second source before relying on the update guidance at the top of the history. WordPress's documentation says the Plugins screen gives the version number in its Description column and displays an update notice when the Plugin Directory holds a newer version. Write down both.
Record two connections. The first is the plugin's own API service. The listing's installation steps describe a "Generate API Key" button on the plugin's dashboard that activates the event monitoring and generates a key for what they call the remote Sucuri WordPress API service: note whether it is on offer.
An upgrade notice in the readme says a past release removed the dependency on a Sucuri API service it calls discontinued, and that to keep using the API communication service "with your own API" you set SUCURISCAN_API_URL in wp-config.php. Note whether that value is set, and to which address.
The second is the firewall key. The listing says a Sucuri Firewall API key is entered under Firewall Management; the vendor's activation article says to find the Sucuri Security plugin on the sidebar and go to Firewall (WAF). Record whether a key is present, never the key itself.
The vendor's alerts article puts an Audit Logs panel on the plugin's dashboard page; the listing's changelog speaks of an Audit Logs page with a CSV download of the complete audit trail. Write down the date of the oldest entry on show, because that changelog mentions "an archive before older records age out", and leave the download unless your authorisation covers taking a copy.
On multisite, the vendor's multisite article says the audit logs, hardening and login information are shared among all the sites in the network, while settings affect only the site where they were applied.
The listing calls this area the Hardening & Prevention section; the vendor's hardening article gives the path Sucuri Security Dashboard > Settings > Hardening > Hardening Options. List each option and whether it has been applied, applying and reverting nothing.
The article says hardening blocks the execution of PHP files in sensitive directories by adding a set of rules to the .htaccess file in each one, and its options name wp-content/uploads, wp-content and wp-includes.
Read the .htaccess file in each of those directories too. For exceptions it gives Security Dashboard > Settings > Hardening > Whitelist Blocked PHP files: copy every entry.
The listing places alert settings in Settings > Alerts. The plugin's help text for its Alerts Recipient panel says that by default alerts go "to the primary admin account, the same account created during the installation of WordPress in your web server", and that more people can be added to the list.
For changing the recipient, the vendor's alerts article gives the path Sucuri Settings -> Alerts -> Alert Events. Change nothing there: copy every address listed, and mark any that belongs to someone who has stopped working on the site.
What a Sucuri Security version match cannot show
Matching the installed version to a record shows exposure to that record.
It leaves open whether the flaw was used on this site, who is on the alert list, which address SUCURISCAN_API_URL points the plugin at, and which PHP files have been excepted from hardening.
A WordPress security audit adds tests that reading a settings screen cannot: it tests each upload path with files that are not what their extension claims, such as SVG or HTML content, to see what the server stores and serves back to other users, and it checks whether the built-in plugin and theme file editor has been switched off.
Frequently asked questions
Its affected range and patched versions field give all versions up to and including 1.8.33, with 1.8.34 listed as patched. Compare the installed version with every range in the history on this page, then read the update guidance at the top of the history.
The slug is sucuri-scanner, and the listing's installation steps say to type "sucuri" or "sucuri-scanner" in the search box and install the option with "By Sucuri Inc." at the foot. The listing's heading begins Sucuri Security. Whichever name a report uses, match on the slug and the version fields.
The records are those the source data files under the slug sucuri-scanner, and being filed there does not settle the question for a paid product. The listing's FAQ says the premium and the free version share the same codebase, with a few extra features unlocked by a Sucuri Firewall API key, and that the Website Firewall runs in the cloud without the need of anything installed.
The listing's FAQ asks "Do the logs get stored to my database?" and answers "No, they do not." The plugin's help text for its API Service Communication panel says that once the API key is generated and SUCURISCAN_API_URL is set, the plugin communicates with a remote API service that acts as data storage for the audit logs. Note whether your site has that set up.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to every record listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- Sucuri Security <= 1.8.33 - Cross-Site Request Forgery (CVE-2022-29489)