Threats Tagged 'cwe-200'

The Password Protected WordPress plugin version 2.6.8 contains an information exposure vulnerability that allows unauthenticated users to bypass the sitewide password protection and access protected content and account identifiers via the REST API. This issue is a regression of a previously fixed vulnerability (CVE-2024-0437) that was patched in version 2.6.7 but reintroduced in 2.6.8. No official patch or remediation guidance is currently provided.

## Summary The Postgres and SQLite stores persist hierarchical namespaces as a dot-joined string (`("memories", "alice")` becomes `memories.alice`) and scoped reads by matching that string with `LIKE '<path>%'`. Because `LIKE` has no notion of the `.` separator, a scoped `search` or `list_namespaces` also matched sibling namespaces whose flattened form shares leading characters. Applications commonly use the namespace as a tenant boundary. Where they do, a read scoped to one namespace could return items belonging to another, without any crafted input — an ordinary scoped request was sufficient. We have no evidence of this behavior being exploited in the wild. ## Affected users / systems You may be affected if you: - use `PostgresStore`/`AsyncPostgresStore` or `SqliteStore`/`AsyncSqliteStore`, and - rely on the namespace to separate data between users or tenants, and - have namespace labels where one is a prefix of another (`1` and `12`, `alice` and `alice2`), or labels containing `_` or `%` Applications whose namespace labels are fixed-length identifiers such as UUIDs, containing no `_` or `%`, are not affected — no such label can be a prefix of another. `InMemoryStore` compares namespaces element-wise and is not affected. Three distinct cases were possible: - **Sibling namespaces.** A read scoped to `("foo",)` also returned items under `("foobar",)` and `("foo2",)`. - **Unescaped pattern metacharacters.** `_` and `%` are legal namespace labels — only `.` is rejected — but were interpolated into the match pattern unescaped, so `("user_1",)` also matched `("userX1",)`. - **Suffix conditions.** `list_namespaces(suffix=("alice",))` also matched the sibling leaf `users.malice`. This is not SQL injection. Values were passed as bound parameters and never interpolated into statement text; the bound value *was itself* a `LIKE` pattern whose metacharacters were not neutralized. ## Impact - Confidentiality: disclosure of stored items belonging to namespaces outside the caller's intended scope, where namespaces are used as a tenant or user boundary. - No integrity or availability impact. `get`, `put`, and `delete` compare namespaces with `=` and were never affected; the issue is limited to read paths. ## Patches / mitigation Prefix scoping now matches the namespace exactly or requires the `.` separator before any remainder, pattern metacharacters in labels are escaped, and `list_namespaces` uses segment-aware matching for both prefix and suffix conditions. On SQLite, the descendant match moved from `LIKE` to `GLOB`. `LIKE` is case-insensitive for ASCII in SQLite, so scoped reads previously matched namespaces differing only in case, while `get`/`put`/`delete` treated them as distinct. Search now agrees with them. Upgrade to `langgraph-checkpoint-postgres` 3.1.1 or `langgraph-checkpoint-sqlite` 3.1.1. ## Compatibility `*` in a `list_namespaces` match path now spans exactly one namespace segment. This restores the documented behavior — `NamespacePath` documents `("cache", "*", "v1")` as "any cache category with v1 version" — and matches `InMemoryStore`. Multi-segment matching was an artifact of translating `*` into a SQL `%` wildcard, the same mechanism responsible for this issue, and could not be preserved while fixing it. Callers relying on the previous behavior can express "match at any depth" by combining both match conditions, which are ANDed: ```python list_namespaces(prefix=["uid"], suffix=["alice"]) ``` Applications whose namespace labels cannot be prefixes of one another see no behavioral change. ## Operational guidance - Prefer fixed-length namespace labels such as UUIDs, so no label can be a prefix of another. - Where labels are user-supplied, validate them at the boundary rather than relying on scoping alone. ## LangSmith / hosted deployments note Unlike previous store advisories, this issue does reach hosted deployments. LangSmith deployments default to `LANGGRAPH_STORE_BACKEND=python`, which uses `AsyncPostgresStore` from `checkpoint-postgres`. Deployments configured with `LANGGRAPH_STORE_BACKEND=grpc` use a separate implementation that received an equivalent fix.

Statamic CMS versions prior to 5.74.1 and 6.24.0 contain a vulnerability where an authenticated Control Panel user can verify the existence of an email address in the system via a user creation wizard endpoint. This endpoint does not require permission to view users and only reveals whether the email corresponds to an existing user, without exposing additional user data. The issue has been fixed in versions 5.74.1 and 6.24.0.

CVE-2026-5336 is a vulnerability in the DataPress (Dataverse Integration) WordPress plugin before version 2.91. It improperly restricts access to its template rendering feature, allowing users with Contributor role or higher to disclose sensitive information, including session cookies of higher privileged users who view the affected content. This vulnerability can lead to unauthorized data disclosure.

OpenReception's appointment booking software prior to version 1.0.2 exposes the full tenant record, including the PostgreSQL connection string with superuser credentials, to any authenticated TENANT_ADMIN of that tenant. This exposure allows a TENANT_ADMIN to access and manipulate all tenant databases and the central database, breaking tenant isolation. Version 1.0.2 addresses this issue.

OpenReception's appointment booking software prior to version 1.0.5 contains an information exposure vulnerability. The unauthenticated /api/tenants/{id}/schedule endpoint discloses details of all non-archived channels for a tenant regardless of their intended visibility. Channels marked as private (isPublic = false) are meant to be hidden but are exposed, revealing channel names, descriptions, IDs, agent associations, pause status, confirmation requirements, and slot availability. This issue was fixed in version 1.0.5.

A vulnerability was found in heshengtao super-agent-party up to 0.4.1. This affects the function get_file_content of the file server.py of the component execute_tool_manually Endpoint. The manipulation of the argument tool_name/tool_params results in information disclosure. The attack can be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

CVE-2026-60023 is a high-severity vulnerability in Apache Answer that allows unauthorized users to access deleted or pending answers through the single-answer read path if the parent question remains visible. This exposure of sensitive information could lead to unauthorized disclosure of answer content that should have been inaccessible. The issue affects Apache Answer versions prior to 2.0.2. Upgrading to version 2.0.2 resolves the vulnerability.

Dell Virtual Storage Integrator for VMware vSphere Client, versions prior to 10.11.1.0, contain(s) a Sensitive Information Disclosure vulnerability. An unauthenticated remote attacker could potentially exploit this vulnerability, leading to information disclosure and session hijacking. This vulnerability is considered critical as it allows an unauthenticated attacker to obtain active session credentials and fully impersonate authenticated users, including administrators. Dell recommends customers to upgrade at the earliest opportunity.

The system accepts authentication requests without sufficient validation to enforce tenant isolation when using Email OTP, SMS OTP, or Magic Link as first-factor authenticators. This failure to adequately separate user data between tenants can lead to the exposure of personally identifiable information. Successful exploitation allows an attacker to disclose personally identifiable information of users in different tenants, resulting in privacy violations and potential regulatory non-compliance. This may include unauthorized access to user details such as mobile numbers.