Security advice, made clearer

A security issue has been reported in RSS Aggregator by Feedzy. Site owners should check whether the plugin is installed and review the publisher’s current remediation guidance.

A published security issue affects certain configurations of the Contact Form by Supsystic WordPress plugin. Here is what site owners should check and what the finding does—and does not—mean.

A published security advisory affects vTables versions before 0.3. Here is how to check your site and decide what to do next.

A security advisory concerns the Password Protected plugin and its bundled Freemius software component. Here is what the finding means and what to check.

A flaw in Contact Form by Supsystic affects versions before 1.11.1. Site owners should check the installed 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 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 security issue in the toml-node parser can make a Node.js process unresponsive when it handles a specially prepared TOML document. Here is how to check what version is in use and what to do next.

A reported resource-exhaustion weakness in Apache bRPC can cause disproportionate memory use and process crashes. Here is how to check your exposure carefully.

A high-severity issue can allow a remote Redis server to crash an Apache bRPC client process in a specific configuration. Here is what affected teams should check.

A flaw in vLLM can allow Python code to run in the API process under specific model and configuration conditions. Here is what operators should check.

A published vulnerability affects sqlparse versions up to and including 0.6.0. Here is what site owners and maintainers should check, without assuming that an affected version has been compromised.