VYPR
Medium severity6.5NVD Advisory· Published Jun 15, 2026· Updated Jun 15, 2026

CVE-2025-69332

CVE-2025-69332

Description

WordPress Bookify plugin <=1.1.1 allows subscribers to access higher-privileged actions due to missing authorization checks.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

WordPress Bookify plugin <=1.1.1 allows subscribers to access higher-privileged actions due to missing authorization checks.

Vulnerability

The WordPress Bookify plugin versions up to and including 1.1.1 contain a broken access control vulnerability. The plugin fails to properly authorize or validate nonce tokens in certain functions, allowing unprivileged users to perform actions intended for higher-privileged roles [1].

Exploitation

An attacker must have a subscriber-level account on the WordPress site. No additional authentication, network position, or user interaction beyond having a low-privilege account is required [1]. The attacker can execute functions that lack proper authorization checks by sending crafted requests to the vulnerable endpoints.

Impact

Successful exploitation enables the attacker to perform actions normally restricted to higher-privileged users, such as administrators [1]. This can lead to unauthorized data access, modification, or other privilege escalation outcomes, depending on the affected functions.

Mitigation

The vulnerability is fixed in version 1.1.2 [1]. Users should update the Bookify plugin to version 1.1.2 or later immediately. As a workaround, Patchstack provides a mitigation rule to block attacks until the update is applied [1]. The vulnerability is considered moderately dangerous and is expected to be used in mass-exploit campaigns [1].

AI Insight generated on Jun 15, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.