Website Security Software Resources
Glossary Terms, Discussions, and Reports to expand your knowledge on Website Security Software
Resource pages are designed to give you a cross-section of information we have on specific categories. You'll find feature definitions, discussions from users like you, and reports from industry data.
Website Security Software Glossary Terms
Cybersecurity refers to actions taken to combat threats against networked systems, devices, and applications. Learn more about the different kinds.
Explore our Technology Glossary
Browse through dozens of terms to better understand the products you purchase and use everyday.
Website Security Software Discussions
I've got WP Cerber installed and it works great, especially after my site was hacked a couple months ago. When it got hacked, I saw a shed load of nonsense pages created like /garden-furniture/dwkwng-13135 etc. I don't really know how to get rid of these pages? For example, this shows that someone was trying to look for vulnerable code: www.sukimarketing.co.uk/Cake-Toppers-411839-Cupcakes-toppers-birthday-unicorn.shtm Excuse my total ignorance! I don't quite understand how it works, but do these pages actually exist in my site somehow? How can I get rid of them? There's SO many.
Hi there, After toggling the "Disable wp-login.php" setting on, wp-login.php is still accessible (from an incognito window, from another browser, even after dumping browser cache). I've purged all of the site's caches (siteground, cloudflare) and the problem remains--is this a bug in the plugin, or something to do with my site? I followed the procedure here: https://www.g2.com/products/cerber-security-antispam-malware-scan/discuss with the exception of the "Request wp-login.php" setting. Thanks for your help!
I've read this wpcerber section: https://wpcerber.com/restrict-access-to-wordpress-rest-api/ I have enabled: Block access to users' data via REST API as well as Block access to WordPress REST API except any of the following. My namespaces show as follows: { "namespaces": [ "oembed/1.0", "2fa/v1", "contact-form-7/v1", "yoast/v1", "mc4wp/v1", "wc/store", "wc-analytics", "wc-admin", "testwp", "elementor/v1", "wc/v1", "wc/v2", "wc/v3", "wccom-site/v1", "wp/v2", "wp-site-health/v1" ] } I want to allow Woo Rest API version 3 access and so I have tried adding wc/v3 as well as wc/v3/products to allowed namespaces but when I try to access the api, I am getting the 401 message. // 20201221161556 // https://fee8f3a621.nxcli.net/wp-json/wc/v3/products { "code": "woocommerce_rest_cannot_view", "message": "Sorry, you cannot list resources.", "data": { "status": 401 } } What am I doing wrong?
