Summary
A reported authorisation weakness in GetPaid could let some logged-in, lower-privileged users view or change invoice information. Here is how to check your site and respond carefully.
Searching includes archived guidance. You can change this using Show.
Archived means older guidance—not that the issue is fixed or the software is safe.
903 results
A reported authorisation weakness in GetPaid could let some logged-in, lower-privileged users view or change invoice information. Here is how to check your site and respond carefully.
A public advisory describes an authorisation-bypass vulnerability in the GetPaid WordPress plugin. The affected-versions table shows which releases are in scope; a vulnerable version is not evidence that a site has been compromised.
A reported input-validation weakness in the GetPaid plugin could allow an unauthenticated visitor to bypass payment processing on a public payment form. Here is how to check your position calmly.
A vulnerability has been reported in the WordPress plugin Remove Google Fonts – Disable, Block, or Replace with Bunny Fonts for GDPR Compliance. Here is what site owners should check.
A published advisory describes a high-severity issue in Mobile builder for WordPress. Site owners should check the installed plugin version and follow the publisher’s current guidance.
A reported vulnerability in Froxlor before version 2.3.15 could let logged-in customers create MySQL databases even when an administrator had disabled that feature.
A high-severity information-disclosure issue in Froxlor could expose API credentials to administrators with a particular permission. Here is what website owners should check.
A medium-severity issue in Control Web Panel affects versions before 1.29. There is no confirmed fixed release in the available evidence, so site owners should check the publisher’s current guidance before making changes.
A published advisory describes a high-severity SQL injection issue in Control Web Panel (CWP) versions before 1.16. Here is what to check and what the finding does—and does not—tell you.
A vulnerability has been reported in Control Web Panel (CWP) versions before 1.16. Here is what site owners and administrators should check, and what the report does—and does not—show.
A medium-severity authorisation issue could allow an unauthenticated visitor to view unpublished job-position details in affected Dolibarr installations. Here is what site owners should check.
A reported vulnerability affects Dolibarr ERP CRM versions before 24.0.0. It requires administrator authentication, but could allow operating-system commands to be run as the web server user.
A vulnerability in versions of pypdf before 6.7.1 can make specially crafted PDF files trigger an infinite loop in some circumstances. Here is what to check and how to respond calmly.
A vulnerability in older pypdf versions could make PDF processing take a long time and use substantial memory when handling a specially crafted file.
A vulnerability in older pypdf releases can cause an endless processing loop when a specially crafted PDF’s outlines or bookmarks are accessed. Here is what to check and how to respond calmly.
CVE-2026-22691 may cause unusually long processing times when pypdf reads specially malformed PDF files in non-strict mode. The supplied record does not establish exploitation.
A low-severity issue in older versions of the pypdf Python library could make some invalid PDF files take unusually long to process. Here is what site owners should check.
A reported authentication-bypass weakness affects phpMyAdmin versions up to and including 5.2.3. Here is what to check and how to respond calmly.
A path traversal vulnerability in Moodle’s Blackboard question import format could allow authorised users with particular teaching permissions to copy server files into a draft area. The affected version list does not confirm that any individual site has been compromised.
A medium-severity vulnerability has been reported in phpMyAdmin versions up to and including 5.2.3. Here is what to check and how to respond calmly.
A reported security weakness in phpMyAdmin through version 5.2.3 could let an attacker with an already hijacked session remove two-factor authentication from that session’s account settings.
A security issue in WeGIA could allow an authenticated user to access or alter records belonging to someone else. Here is what site operators should know and do next.
Imagine our servers as big apartment buildings, and each website hosted on it lives in its own apartment.
CageFS acts like a personal security guard for each website, ensuring that they can't peek into or mess with their neighbours' spaces.
At Hipposerve, our priority is more than just hosting—it's ensuring your digital domain remains secure.
Hipposerve® SwampGuard as a vigilant gatekeeper, while our DDoS protection and malware detection work seamlessly in the background.
We all have those “Oops!” moments, don't we? Whether it's spilling coffee or accidentally deleting a file, mistakes are a part of life.
With Hipposerve, you've got a safety net! Every single one of our hosting plans includes a rolling backup as standard.
Independently owned, focused on reliable hosting and personal service.
Modern infrastructure designed to deliver fast, reliable website performance.
Free SSL certificates included with every hosted website.
Automatic daily backups with Hipposerve Rewind to help protect your data.
Proactive monitoring and security features to help protect your website.
We'll move your existing website to Hipposerve at no additional cost.
Friendly technical support from real people when you need it.
Providing reliable hosting, with 99.9% uptime, for customers around the world.
