CVE Vulnerability Catalog

Vulnerability in Oracle Hyperion Calculation Manager (component: Security) version 11.2.25.0.000. Difficult to exploit by an unauthenticated attacker over HTTP, requires user interaction, allowing unauthorized access to critical data or complete access to all data.

Vulnerability in Oracle Hyperion Calculation Manager (component: Security) version 11.2.25.0.000. Easily exploitable by a high-privileged attacker with logon to the infrastructure, may impact other products (scope change) and allows unauthorized access to critical data and modification of data.

Vulnerability in Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition (component: Networking). Affects multiple versions. Difficult to exploit by an unauthenticated attacker over HTTP, may impact other products (scope change) and allows unauthorized access to critical data or complete access to all data.

Vulnerability in Oracle Enterprise Manager Base Platform (component: Enterprise Manager Install) affects versions 13.5 and 24.1. It is difficult to exploit, requires logon to the infrastructure, and a low-privileged attacker can gain unauthorized access to critical data or all data of the platform. Attacks may impact additional products (scope change).

Vulnerability in Oracle Learning Management (component: Internal Operations) affects versions 12.2.3-12.2.15. It is easily exploitable by an unauthenticated attacker via HTTP, allowing unauthorized update, insert, or delete access to some data and read access to a subset of data.

Vulnerability in Oracle Public Sector Financials (International) (component: Authorization) affects versions 12.2.3-12.2.15. It is easily exploitable by a low-privileged attacker via HTTP, allowing unauthorized update, insert, or delete access, read access to a subset of data, and partial denial of service.

Vulnerability in Oracle Unified Directory (component: OUD Core) affects versions 12.2.1.4.0 and 14.1.2.1.0. It is difficult to exploit, requires low privileges and LDAP access, allowing unauthorized creation, deletion, or modification of critical data and full access to data.

Vulnerability in PeopleSoft Enterprise PeopleTools (component: Panel Processor) affects versions 8.61-8.63. It is difficult to exploit, requires low privileges, HTTP access, and user interaction, allowing unauthorized update, insert, or delete access and read access to a subset of data. Attacks may impact additional products.

Vulnerability in Service Delivery Platform (component: Messaging Enabler) affects version 14.1.2.0.0. It is easily exploitable by an unauthenticated attacker via HTTP, allowing unauthorized update, insert, or delete access and read access to a subset of data.

Vulnerability in Service Delivery Platform (component: Messaging Enabler) affects versions 14.1.2.0.0 and 12.2.1.4.0. It is easily exploitable by a high-privileged attacker via HTTP, allowing unauthorized access to critical data or full access to data. Attacks may impact additional products.

Vulnerability in Oracle Workflow (component: Worklist) affects versions 12.2.3-12.2.15. It is easily exploitable by a low-privileged attacker via HTTP, allowing unauthorized access to critical data or full access to data.

Vulnerability in Oracle Hyperion Financial Reporting (component: Repository) affects version 11.2.25.0.000. It is easily exploitable by an unauthenticated attacker via HTTP, allowing unauthorized update, insert, or delete access and read access to a subset of data.

Vulnerability in Froxlor before version 2.3.8. The lib/ajax.php entry point bypasses centralized request validation, and the editapikey action does not validate a CSRF token. An unauthenticated attacker can induce an authenticated administrator's browser to submit a forged request that adds an attacker-controlled address to an API key's allowed_from list or removes its expiration, weakening the key's security restrictions.

Froxlor before version 2.3.8 has a vulnerability in the DomainZones.add API command that does not reject line delimiters, tab characters, semicolons, or unsupported DNS record types before serializing values into a BIND zone file. An authenticated customer with DNS-zone permissions can inject additional resource-record lines, bypassing field-level validation. BIND accepts the injected records, allowing modification of DNS data and potential DNS availability impact.

Blueprint Studio before version 2.5.2 returns raw exception strings in API responses to authenticated Home Assistant users. Some exception messages may contain internal filesystem paths or implementation details. The disclosed information could help an authenticated user fingerprint a Home Assistant installation and refine follow-up attacks.

Blueprint Studio before version 2.5.2 in the legacy stateless terminal command execution path accepts a cwd working-directory parameter and checks only whether the directory exists, without requiring it to remain inside the Home Assistant configuration directory. An administrator using the restricted terminal helper could select an existing directory outside the intended configuration boundary. Commands could then access or modify host paths permitted by the Home Assistant container and filesystem permissions, weakening the helper's expected filesystem restriction.

Blueprint Studio before version 2.5.2 in terminal SSH key authentication writes SSH private-key material to a file under the Home Assistant configuration directory before applying restrictive permissions and relies on best-effort cleanup. The key could temporarily remain on disk and could persist if cleanup failed or Home Assistant crashed. A user or process with filesystem access to the Home Assistant configuration directory could obtain the residual private key.

Blueprint Studio before version 2.5.2 configured Git's credential.helper store when saving Git credentials, causing Git credential-store to persist usernames and access tokens in plaintext in the .git-credentials file for the user running Home Assistant. Tokens could remain outside Blueprint Studio's intended Home Assistant storage and be read by other users or processes with access to the same filesystem context. The persistent helper configuration also affected later Git operations beyond the immediate Blueprint Studio action.

Koha before versions 26.05.02, 25.11.07, and 25.05.13 contains a stored cross-site scripting vulnerability in the purchase suggestion handler that allows authenticated staff users to inject malicious scripts by submitting unsanitized input through the suggestion save operation. Attackers can supply crafted HTML or script content in fields such as title, author, isbn, publishercode, place, collectiontitle, itemtype, and note, which are stored without sanitization and later rendered in the suggestion list template, causing injected scripts to execute in the browser of any staff user who views the suggestions.

fastify before version 5.12.1 is affected by a schema validation bypass when a request body schema targets a root primitive value. When the schema validates a top-level primitive such as an integer, Ajv can coerce a JSON string into the expected type during validation, but Fastify does not replace the root request body with the coerced value, so the route handler receives the original unvalidated string. As a result, a request that should have failed validation can reach application logic with a value that does not satisfy the schema, which can undermine integrity and access-control checks that rely on the validated type.