Security advice, made clearer

A published security advisory describes a broken access control issue in Content Egg. It could expose product information from unpublished WordPress posts to people who are not signed in.

A reported issue in the Dokan WordPress plugin could affect how a vendor’s unpaid commission is reconciled when a discount coupon is used at checkout. Here is how to check your position without jumping to conclusions.

A published security notice concerns the WordPress plugin Security For WooCommerce. The affected-versions table shows which releases are in scope; no particular website should be assumed affected or compromised without checking.

A published security advisory concerns Essential Real Estate, a WordPress plugin used for property listings. Here is what the finding means and what to do next.

A published advisory describes a missing ownership check in the Essential Real Estate WordPress plugin. It could let a logged-in, low-permission user view another user’s invoice details.

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.

The publisher has reported a high-severity issue in pypdf, a Python library used to read and extract text from PDF files. It is addressed in version 6.18.1.

A flaw in the pypdf PDF library can make an application spend a long time processing a specially crafted PDF. Here is how to check whether your site uses an affected version and what to do next.

A vulnerability in older versions of the open-source pypdf library could use excessive memory when an application reads specially crafted PDF page labels. Here is what to check and how to respond calmly.

A vulnerability in versions of the open-source pypdf PDF library could make specially crafted documents use unusually large amounts of memory and processing time. Here is what to check.

A medium-severity issue in the pypdf Python library can make specially crafted PDFs use excessive processing time and memory. Here is what to check and how to respond sensibly.

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.

A medium-severity security issue in WeGIA can allow harmful content submitted in a memorandum dispatch to run in another user’s browser. Here is what to check and how to respond calmly.

A stored cross-site scripting issue has been reported in WeGIA versions before 3.8.7. Here is what it means for sites using the web manager and what to do next.

A medium-severity issue in the Python library joserfc can increase memory use when specially formed signed tokens are processed. Here is what maintainers should check.

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.