Security advice, made clearer

A security advisory affects User Profile Builder versions up to and including 4.0.3. Here is what the issue means and what administrators can do next.

A serious vulnerability has been reported in the Prime Mover – Backup and Migration WordPress plugin. Here is what to check and what to do next.

A serious issue has been reported in two WordPress plugins. Whether a site is affected depends on the installed software and on how its front-end forms are configured.

A vulnerability in the User Profile Builder plugin could let a Multisite subsite Administrator edit another user’s email address and take over the account through password reset.

Public security records describe a low-severity issue in the Popup Builder WordPress plugin. Here is what it means and what to check.

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 published advisory describes a medium-severity denial-of-service issue in certain versions of svg-sanitizer. Here is what site owners should check and do next.

A high-severity vulnerability in svg-sanitizer could make a website’s PHP workers spend excessive time processing a specially prepared SVG file. Here is what to check and what the available evidence does—and does not—show.

A security issue in older versions of the open-source pypdf library could make an application use excessive memory when opening a specially crafted PDF. Here is how to check whether it is relevant to your site or software.

A high-severity issue in pypdf can cause excessive processing and memory use when an application reads the page count of a specially crafted encrypted PDF.

A flaw in the Python PDF library pypdf can cause excessive memory use when it processes a specially malformed PDF. Here is how to check what your site or application uses.

A vulnerability in the Python joserfc library could allow repeated requests to consume the CPU of a service handling certain encrypted messages. The publisher’s evidence says the issue is fixed in version 1.7.5.

A vulnerability in the pyasn1 library can make certain ASN.1 data take an unusually long time to decode. Here is what site owners and developers should check.

A flaw in pyasn1 can make decoding specially prepared data use excessive processor time. Here is how to check whether a Python application may need attention.

A security advisory concerns pyasn1 versions before 0.6.5. Here is what site owners and developers should check, without assuming that an affected version has been compromised.

A flaw in the Python pyasn1 library can make decoding specially constructed data consume increasing amounts of CPU. Here is how website owners and developers can check their position.