Authenticated users holding the plugin's booking-provider role on WordPress sites running Hydra Booking - Appointment Scheduling & Booking Calendar before 1.2.2 can cancel and permanently delete bookings belonging to other providers, because two booking endpoints act on a supplied booking identifier without confirming that the booking belongs to the requesting user. The issue is a classic insecure direct object reference (CWE-639) and is only meaningful on installations that host multiple providers, so single-provider sites gain no adversarial advantage. Publicly available exploit code exists, but no active exploitation has been confirmed (no CISA KEV listing), and the practical risk remains low: the attacker must already hold a legitimate provider account and the outcome is limited to integrity (cancel/modify) and availability (deletion) impact on booking records, with no confidentiality exposure.
Unauthenticated visitors to WordPress sites running the Secure Custom Fields plugin before 6.9.4 can submit data against a registered form other than the one that was actually rendered to them, overwriting the title and content of the post that the abused form is bound to. The vulnerability is only reachable where SCF's front-end form-submission feature is actively deployed and rendered publicly, and successful exploitation requires the attacker to enumerate a second registered form plus its bound post, which is why the assessed CVSS is a modest 3.7 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - integrity-only, low impact). Publicly available exploit code exists (the WPScan entry is tagged as an exploit reference), but there is no KEV confirmation of active exploitation; the vendor has released a fix in Secure Custom Fields 6.9.4, so the practical priority is patching sites that use front-end forms rather than emergency response.
Stored cross-site scripting in the Business Name Generator WordPress plugin through version 1.3 allows an authenticated high-privilege user (administrator) to inject malicious script into the plugin's unsanitised settings fields, which then executes when a second privileged user renders the affected settings page. Publicly available exploit code exists, but exploitation is tightly constrained: it requires high privileges, victim interaction, and a configuration where the unfiltered_html capability is withheld from admins, chiefly WordPress multisite networks, making this a low-priority, high-CVSS-noise-floor issue rather than a genuine threat. No vendor-released patch was identified at time of analysis.
An authenticated low-privilege user of the Grimmory (BookLore) self-hosted library service can read book files belonging to other accounts by tampering with the bookId argument passed to the Kobo download endpoint handled by KoboController.streamFileToResponse, an IDOR-style authorization bypass (CWE-639) rated CVSS 5.3 with confidentiality-only impact. Publicly available exploit code exists, and although upstream issue #2431 is closed as completed, its only comment states the report 'has already been reported elsewhere' with no fixing commit or pull request identified there. No KEV listing or independent evidence of active exploitation was found, so real-world risk depends on whether the instance is network-reachable to an attacker who already holds valid credentials and whether the Kobo download feature is exposed.
An incorrect authorization check in Grimmory (grimmory-tools/grimmory, published as BookLore) up to versions 3.3.3 and 3.4.1 lets any authenticated low-privilege account read admin-scoped application settings through the Settings API endpoint GET /api/v1/settings, because AppSettingController.getAppSettings returned the full settings map without filtering entries by the caller's PermissionType (ADMIN / MANAGE_METADATA_CONFIG). The exposure is configuration data - integration flags, OIDC session/group-sync settings, Kobo/Komga/OPDS toggles and metadata-provider configuration - not credentials or write access; the case is assessed at low severity (CVSS 4.0 base 2.1; independent CVSS 3.1 assessment AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) and no KEV exploitation is recorded. Publicly available exploit code exists (referenced GitHub issue 2430) and the issue is rated low real-world risk despite the 'Authentication Bypass' tag, since the attacker must already hold a valid account and only gains read access to settings.
Stored cross-site scripting in the PHP-FTS full-text search library (olivier-ls/php-fts) through version 1.1.2 lets an attacker who can introduce content into the search index inject markup that executes in a victim's browser when the application renders the returned search highlights as HTML. The flaw sits in SearchEngine::buildHighlights in src/SearchEngine.php, which concatenates stored field text with opening and closing highlight tags without escaping it; per the vendor's own CVSS:4.0 vector the attacker is an authenticated remote user (PR:L) and exploitation requires the victim to interact (UI:P), with impact limited to manipulated content (VI:L) and no confidentiality or availability loss. The vendor shipped a fix in 1.1.3 (commit 0b2fae333d6b022da7ed4c43e2d41aa03f91dff3) and publicly available exploit code exists for this issue, but there is no indication of confirmed active exploitation in the wild.
Out-of-bounds bad_words token indices in vLLM through 0.29.0 are not validated against the model's generation output width, allowing the indices to be written past the logits buffer and corrupt the sampling state of concurrently batched requests, so unrelated in-flight HTTP requests can receive incorrect output tokens. Exploitation requires API access sufficient to submit sampling requests with a bad_words parameter (authenticated, PR:L), a target model whose tokenizer exposes input-only placeholder tokens with IDs above the model's logits vocabulary (typically multimodal models such as those with <|audio|> tokens), and concurrent requests sharing the batch, so a text-only model whose tokenizer vocabulary equals its output vocabulary is not affected. No public exploit code has been identified at time of analysis and there is no KEV listing; the issue is a low-severity integrity/quality-of-output defect rather than a confidentiality or availability compromise, and an upstream fix is available as a pull request.
Path traversal in rclone before 1.75.1 allows object names returned in server or third-party directory-listing responses to contain forward slashes and '../' parent-directory references that are not confined to the listed directory, so a malicious or compromised source can attempt to steer writes outside the transfer destination root. Exploitation requires the victim to run rclone against an attacker-influenced remote (attacker-controlled source), user interaction to initiate the transfer, and high attack complexity; the local backend's existing downstream protections currently block actual file escape on the default local backend, keeping real-world impact limited. Rated only 2.3 (CVSS 4.0) and assessed as CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N, this is a low-priority defense-in-depth hardening issue rather than an actionable threat, and no public exploit code was identified at time of analysis (no CISA KEV listing).
Cross-site scripting in Hono before 4.13.7 allows unauthenticated remote attackers to inject arbitrary HTML and execute script in a victim's browser under the application's origin when the application uses hono/jsx server-side rendering in one of four specific patterns involving plain strings: as a child or fallback of Suspense, as a string child of ErrorBoundary alongside an asynchronous sibling, as the single child of Context.Provider, or as the root value passed to renderToString() or renderToReadableStream() from hono/jsx/dom/server. Exploitation requires attacker-controlled data to flow directly into those strings during SSR and a victim to load the rendered output, making this a low-priority XSS despite the network attack vector and no authentication requirement. No public exploit code has been identified at time of analysis, and the issue is fixed in Hono 4.13.7.