Improper authentication in AhsayCBS up to version 10.3.2 lets an unauthenticated remote attacker bypass credential verification by manipulating the 'random' parameter processed by the checkSysPwd routine in the API component (com/ahsay/obs/api/ApiStructsAction.java). Exploitation requires only network reachability to the exposed AhsayCBS API/management interface and publicly available exploit code exists, so deployments that leave the console internet-facing or broadly reachable are the most at risk. The assessed impact is limited to partial confidentiality, integrity, and availability effects, and no confirmed active exploitation (CISA KEV) has been reported, making this a moderate-priority issue that is nonetheless straightforward to trigger where the API is exposed.
Stored cross-site scripting in the WordPress plugin Horizontal Scrolling Announcements (all versions through 2.6) allows an authenticated user holding access to the plugin's announcement management page - Contributor level or higher, once that permission is granted - to save a payload into an unsanitised announcement setting that is rendered unescaped into an HTML attribute on the front end, so the script executes in the browser of anyone viewing the announcement. Publicly available exploit code exists (the WPScan disclosure is referenced as an exploit source), but EPSS is only 0.15% (4th percentile) and there is no confirmed active exploitation (not listed in CISA KEV). Our independent assessment places real-world priority as LOW: exploitation is not remote-unauthenticated, it is limited to one specific setting, and it additionally requires victim interaction (someone must load a page that renders the stored announcement).
SQL injection in RainyGao DocSys (up to version 2.02.85) allows an attacker to inject arbitrary SQL through the 'url' argument handled by BaseController.createDBForMysql in the Database Management component, potentially exposing or altering backend data. Publicly available exploit code exists, and the CVSS 4.0 vector scores the issue 6.9 (AV:N/AC:L/AT:N/PR:N/UI:N with E:P), while an independent assessment using CVSS 3.1 rates it AV:N/AC:L/PR:L/UI:N with low confidentiality, integrity, and availability impact - the discrepancy regarding privilege requirements reflects the fact that the vulnerable function configures a MySQL connection, an action that in practice is reached from the DocSys management interface and may require an authenticated or administrative session. The vendor was notified via an issue report but has not responded, and no vendor-released patch has been identified at time of analysis.
Information disclosure in Weaviate Verba 2.1.3 and earlier allows remote, unauthenticated attackers to retrieve environment and configuration data by invoking the get_environment function in goldenverba/components/util.py through the generate_stream endpoint. Publicly available exploit code exists (referenced in the VulDB disclosure and a public gist), raising the likelihood of opportunistic scanning, although there is no confirmation of active exploitation (not listed in CISA KEV). Impact is bound to confidentiality (partial disclosure), yielding a 6.9 CVSS v4.0 base score; the main practical prerequisite is that the Verba service be network-reachable.
Unauthenticated remote attackers can exploit a server-side request forgery (SSRF) in SciPhi-AI R2R 3.6.6 and earlier by supplying a crafted generation_config.api_base value to the Retrieval Completion API endpoint, causing the server to make requests to arbitrary internal or attacker-controlled URLs. Publicly available exploit code exists (a GitHub Gist), and the vendor did not respond to disclosure, so no patched version is confirmed at time of analysis. The independent assessment rates this as medium severity (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L; VulDB CVSS 4.0 score 6.9), with impact bounded by what internal targets the R2R server can reach.
Hard-coded JWT signing secrets in SciPhi-AI R2R through 3.6.6 can let remote unauthenticated attackers forge valid JSON Web Tokens and bypass authentication when a deployment still uses the shipped DEFAULT_BCRYPT_SECRET_KEY or DEFAULT_NACL_SECRET_KEY values. The exposure is configuration-dependent: instances that override both defaults with custom secrets are not vulnerable, and the authentication or API endpoints must be reachable over the network for exploitation. Publicly available exploit code exists via the linked disclosure, but there is no KEV confirmation of active exploitation.
SQL injection in the 'location' parameter of admin/donate.php in the kishor-23 food-waste-management-system (PHP, GitHub rolling release) lets remote attackers inject arbitrary SQL into the donation-handling query, exposing or altering backend data. The published CVSS 4.0 vector (6.9, AV:N/AC:L/AT:N/PR:N/UI:N/E:P) asserts unauthenticated, no-interaction exploitation, though the 'admin/' path suggests the page is intended to sit behind an administrative login, so real privilege requirements may be higher if session checks are enforced. Exploit details are publicly available (referenced GitHub issue #7), but the issue is not in CISA KEV, so there is no confirmation of active exploitation in the wild; the vendor was notified and has not responded, and no fixed version exists because the project ships as a rolling release.
SQL injection in the Food Donation Form (fooddonateform.php) of kishor-23's Food Waste Management System allows remote attackers to manipulate the 'image-choice' argument passed to the insert routine, potentially reading or altering data in the backend database. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, E:P) confirms this is remotely reachable with no authentication or user interaction required, and publicly available exploit code exists, so the technical barrier to exploitation is low. However, the product is a niche hobby project distributed via a rolling-release repository with no version pinning and no vendor response to the issue report, meaning real-world exposure depends entirely on whether an operator has deployed and internet-exposed the application - assessed as a LOW priority despite the medium severity score.
SQL injection in the kishor-23 food-waste-management-system delivery/delivery.php Take Order Handler allows unauthenticated remote attackers to read or alter database contents by manipulating the order_id and delivery_person_id parameters. Publicly available exploit code exists (the flaw was reported via a public GitHub issue), and the project has not responded or issued a fix, with its rolling-release model meaning no patched version can be pinned. Real-world impact is limited by the niche deployment of this PHP application, though any internet-exposed instance is at risk of data disclosure or tampering.
Unauthenticated retrieval of other users' stored private files is possible on WordPress multisite installations running the User Private Files plugin before 2.2.0. On multisite, the plugin's rewrite rule - the mechanism that routes file requests through its access check - is never reached, so private files can be fetched directly over HTTP with no credentials, privileges, or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3). Publicly available exploit code exists, but EPSS is only about 0.14% (3rd percentile) and a vendor fix is available in 2.2.0; impact is confined to confidentiality, with no write or code-execution capability.
Arbitrary modification of shipping information on WooCommerce orders is possible in the Razorpay for WooCommerce plugin before 4.8.8, allowing unauthenticated attackers to alter shipping details on orders they do not own. The flaw is a missing authorization check (CWE-639) on a REST API route used during checkout; publicly available exploit code exists, but EPSS is only 0.14% (3rd percentile), indicating low predicted exploitation likelihood, and the vendor has released a patch in version 4.8.8.
Authenticated WordPress users holding Author-level access or above can abuse the schema field default-value resolution feature in the Five Star Business Profile and Schema plugin (versions prior to 2.4.0, including 2.3.20 through 2.3.x) to pull sensitive server-side data into publicly rendered schema output, including other users' password hashes and arbitrary wp_options values, which unauthenticated visitors can then read. Publicly available exploit code exists, but CISA KEV does not list this issue and EPSS is only 0.14% (3rd percentile), so real-world exploitation pressure is low. This is a moderate, not high-urgency, issue: exploitation requires an existing Author or higher account, so sites that never grant that role to untrusted users are not practically exposed, though the vector is network-reachable (CVSS 4.9; CWE-200).
A time-of-check/time-of-use (TOCTOU) flaw in Crossplane's crossplane-runtime package manager (pkg/xpkg/client.go) lets a malicious OCI registry defeat cosign package signature verification, causing an unsigned or tampered package to be installed in place of the verified one. Exploitation requires an unusual combination of non-default operational choices: signature verification enabled through the ImageConfig mechanism, packages installed by mutable tag reference (such as a semantic version) instead of an immutable digest, and installation from a registry the operator does not control, where the attacker can serve a signed image for the cosign verifier and a different unsigned image moments later for the fetch. Impact is limited to integrity - an unverified package is pulled and installed - with no direct confidentiality or availability effect, and no public exploit code has been identified at time of analysis. Fixes are available in crossplane-runtime v2.2.3, v2.3.3, and v2.4.0-rc.1.
Information disclosure in SiYuan before 3.8.5 allows publish-mode readers to extract backlink block IDs (refIDs) and reference counts (refCount) belonging to password-protected or publish-disabled documents by POSTing a published document ID to /api/block/getDocInfo or /api/block/getDocsInfo. The attacker only needs network reachability to the publish endpoint and knowledge of a valid published document ID - no authentication is required per the CVSS vector (PR:N) - and the exposed data is metadata about hidden referencing blocks rather than the protected documents' content. Exploitation requires the instance to actually be running in publish mode with at least one published document that is referenced by a protected or unpublished note; there is no public exploit identified at time of analysis, and a vendor fix is available in SiYuan 3.8.5.
AIIR (invariant-systems-ai aiir) versions prior to 1.7.0 contain fail-open verification and policy gate flaws that allow unauthenticated remote attackers to bypass signature verification controls. When a downstream consumer relies on an affected gate-such as the require_signing policy gate, the CI verification path, the release-verification gate, or a signature-verification path-an attacker can supply an unsigned, forged-bundle, or non-conforming receipt and the gate will falsely report 'verified' or success. This results in low integrity impact (no confidentiality or availability impact) and affects only released versions below 1.7.0; no public exploit code has been identified at time of analysis, and the vulnerability is fixed in 1.7.0.
Path traversal in the Drogon C++ web framework's static file router (StaticFileRouter::route) lets unauthenticated remote attackers read files outside the configured document root on Windows deployments up to and including 1.9.13-1 and 10.0-beta.3. The flaw is limited to information disclosure - no integrity or availability impact - but publicly available exploit code exists and the vendor was contacted early and did not respond, so no official fix is confirmed. Our assessment rates this as a moderate, non-emergency priority: the platform must be Windows, static-file serving must be enabled and reachable, and the payoff is bounded to files readable by the server process; there is no confirmation of active exploitation (CISA KEV).
SQL injection in mooSocial versions up to 3.2.4 allows remote, unauthenticated attackers to manipulate the 'rating' parameter on the /stores/all-products endpoint, potentially leading to unauthorized data access or modification. This moderate-risk vulnerability has a publicly available exploit, but there is no confirmation of active exploitation in the wild. The vendor was contacted but did not respond, and no official patch is available, making mitigation challenging for exposed instances.
Authentication token forgery in topoteretes cognee through 1.5.4 lets a remote attacker who can reach the API mint valid JWTs without any account, because the application signs tokens with the publicly known literal "super_secret" whenever the FASTAPI_USERS_JWT_SECRET environment variable is left unset. Because that fallback is the shipped default behavior, unconfigured or default deployments are exposed, and the same pattern affects the password-reset and email-verification token secrets; successful forgery yields full compromise of confidentiality, integrity, and availability of the cognee instance. Upgrading to 1.6.0 removes the shared fallback entirely and replaces it with a per-process random secret; no public exploit code was identified at time of analysis, and CISA KEV does not list this issue.
Cross-organization information disclosure in ZITADEL 3.0.0 through 3.4.15 and 4.x before 4.17.3 allows an authenticated user who holds an organization-scoped user.read permission to retrieve the authentication method types registered by users in other organizations by calling GET /v2/users/{userId}/authentication_methods. The User Service API validates user.read against the caller's own organization rather than the organization that owns the target user (CWE-863 incorrect authorization), so tenant isolation is broken on multi-organization deployments. Exploitation requires a valid account with org-scoped user.read (PR:L per the assessed vector) and knowledge or enumeration of foreign-org user IDs; impact is limited to method-type disclosure with no credential, token, or account modification exposure, and no public exploit code was identified at time of analysis. CVSS 4.0 base 5.3 and our independent assessment of 5.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) agree that this is a medium-severity confidentiality issue.
Cross-account secret replication in devopspolis secrets-replicator up to and including 0.4.0 silently drops the configured External ID, so the confused-deputy safeguard that operators believe protects the destination role is never actually enforced. An attacker who already holds or can influence an AWS principal that is permitted to assume the destination role (CVSS PR:L, requiring some standing in the trust relationship) can therefore assume it without supplying the External ID, resulting in incorrect permission assignment and limited confidentiality and integrity impact (CVSS 5.3, CWE-732). The flaw affects only deployments that use cross-account AssumeRole replication and rely on external_id for isolation; single-account deployments and configurations that never used an External ID are not impacted. Patches ship in v0.5.0 (commit b42239405fbf4fae3c3f0048fc0b4225112edceb) and no public exploit code or confirmed active exploitation has been identified at time of analysis.
Privilege escalation in ezBookkeeping 1.2.0 through 2.0.0 lets an attacker who already holds a short-lived and/or IP-restricted API token exchange it for a full 30-day normal session token by calling POST /api/v1/tokens/refresh.json, because TokenRefreshHandler never verifies the token type before minting a replacement. The resulting session token outlives the original API token's expiry and its IP allowlist, though impact stays within the compromised account's own scope (low confidentiality and integrity impact). Rated CVSS 5.3 (CVSS:4.0 AV:N/AC:L/AT:N/PR:L/UI:N), it requires a prior valid API token (authenticated) and is fully remediated in v2.0.1; no public exploit code or confirmed active exploitation was identified at time of analysis.
Out-of-bounds read in NASA cFS through 7.0.1 can be triggered by a remote attacker who already holds high privileges and can supply a crafted input file name to the CFE_FS_ParseInputFileNameEx parser, producing only a low availability impact with no confidentiality or integrity loss. The flaw is in the cfe file-system module (cfe/modules/fs/fsw/src/cfe_fs_api.c), and the only identified fix is an upstream pull request that awaits acceptance, so no vendor-blessed patched release is confirmed. No public exploit identified at time of analysis.
Stored cross-site scripting in YesWiki's Bazar 'valeur' action (all versions before 4.6.7) allows an authenticated page editor to point the action's 'url' argument at an attacker-controlled HTTP(S) server whose returned BAZ_fiche_titre markup - for example an <img> tag carrying an onerror handler - is rendered without escaping, so the injected script executes in the browser of every visitor who views the affected page. The impact is constrained by its prerequisites: the attacker needs an existing editor-level account (PR:L) and must induce victim page views (UI:R), yielding low confidentiality and integrity impact with changed scope, consistent with the medium CVSS 4.0 base score of 5.1 and the assessed CVSS 3.1 vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. This is a genuine but moderate-priority CWE-79 issue; no public exploit identified at time of analysis, and the vendor has released a patch in YesWiki 4.6.7.
Sensitive information embedded in outbound responses from the Mindio Magic MCP WordPress plugin (versions through 0.5.6) can be retrieved by a remote, authenticated attacker holding only low-level privileges on the affected site (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N). The flaw is a CWE-201 'Insertion of Sensitive Information Into Sent Data' condition, meaning the plugin places data into responses it transmits rather than leaking it through a separate storage or traversal bug. Impact is limited to confidentiality (information disclosure) with no integrity or availability effect, and there is no public exploit identified at time of analysis and no CISA KEV listing, so real-world urgency is low-to-moderate. The CVSS base score of 4.3 reflects that an attacker must already possess a valid WordPress account on the target site before the disclosure is reachable.