AI Engine Plugin EUVD-2026-78296

Exploitation requires all of the following: (1) a valid WordPress account with at minimum subscriber-level role - unauthenticated access is not possible; (2) the AI Engine plugin's 'Public API' module must be explicitly enabled in plugin settings - when disabled, the REST route does not exist and requests return HTTP 404, completely blocking exploitation; (3) target users must have uploaded audio attachments for which the plugin has generated transcriptions. Exploitation is limited to read-only access to transcribed text - the underlying audio binary files are not exposed. The non-default configuration requirement and mandatory authentication materially reduce the realistic attack surface relative to the raw CVSS 6.5 score.

The NVD/Wordfence CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) is largely accurate. Two factors materially constrain real-world risk beyond what the score conveys: first, a valid WordPress account at subscriber level or above is required, restricting the attacker pool to authenticated users; second, the Public API module must be explicitly enabled - the endpoint does not exist in default plugin configurations, meaning the majority of installations may not be exposed at all. The confidentiality impact (C:H) is scoped to transcribed text content of private audio attachments, not the audio binaries themselves; sensitivity varies by site usage (e.g., private voice memos or confidential recorded meetings could be high-value). No CISA KEV listing is present and no EPSS score was supplied, indicating no confirmed active exploitation at time of analysis. The combination of required authentication, non-default configuration, and read-only confidentiality-only impact makes this a genuine but bounded risk, best prioritized on sites where the Public API module is knowingly enabled and where private audio transcription content is sensitive.

An attacker registers a free subscriber account (or compromises an existing low-privilege account) on a WordPress site running AI Engine ≤3.7.7 with the Public API module enabled, then issues authenticated REST API requests to the transcription endpoint, incrementing integer values in the mediaId parameter. Because WordPress attachment IDs are sequential, the attacker systematically harvests transcribed text from private audio attachments uploaded by other users and administrators without any additional privilege escalation.