What is the CVSS score of EUVD-2026-44874?

EUVD-2026-44874 has a CVSS 3.1 base score of 5.9 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N. EPSS exploitation probability: 0.1%.

Is there a public PoC exploit available for EUVD-2026-44874?

Yes, a public proof-of-concept exploit is available for EUVD-2026-44874. Prioritise patching immediately. EPSS: 0.1%.

Is there a patch available for EUVD-2026-44874?

Yes, a patch is available for EUVD-2026-44874. Update the affected software to the latest version immediately.

AI Engine EUVD-2026-44874

| CVE-2026-12510 MEDIUM

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-07-16 WPScan

GHSA-8rhw-c8ph-cp97

WordPress Authentication Bypass Ai Engine Unknown

5.9

CVSS 3.1 · Vendor: WPScan

Severity by source

Vendor (WPScan) PRIMARY

5.9 MEDIUM

AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N

vuln.today AI

5.9 MEDIUM

Subscriber authentication required (PR:L), identifier enumeration adds complexity (AC:H); full read of targeted conversation (C:H), limited write via record overwrite (I:L), no availability impact.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N

4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 16, 2026 - 16:26 vuln.today

CVSS changed

Jul 16, 2026 - 16:22 NVD

5.9 (MEDIUM)

Patch available

Jul 16, 2026 - 10:18 EUVD

CVE Published

Jul 16, 2026 - 06:00 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 16, 2026 - 06:00 cve.org

MEDIUM 5.9

DescriptionCVE.org

The AI Engine WordPress plugin before 3.5.5 does not verify that a user owns the chatbot conversation referenced by a client-supplied identifier, allowing users with subscriber-level access to read other users' private conversations and take over their conversation records when the discussions feature is enabled.

AnalysisAI

Unauthorized access to private chatbot conversations in the AI Engine WordPress plugin before 3.5.5 allows any authenticated subscriber-level user to both read and overwrite other users' chat records when the discussions feature is enabled. The plugin fails to verify that a client-supplied conversation identifier belongs to the requesting user (CWE-639 IDOR), enabling session data theft and record hijacking. Public exploit code is available via WPScan, though EPSS stands at only 0.13% (3rd percentile), suggesting no widespread automated exploitation; active exploitation is not confirmed in the CISA KEV at time of analysis.

Technical ContextAI

The AI Engine plugin (CPE: cpe:2.3:a:unknown:ai_engine:*:*:*:*:*:*:*:*) implements a chatbot discussions feature that stores per-user conversation records keyed by a client-supplied identifier. CWE-639 (Authorization Bypass Through User-Controlled Key) describes the root cause: the server performs no ownership check between the authenticated session and the requested conversation object, meaning any authenticated user can substitute an arbitrary conversation ID to access or manipulate records belonging to another user. This is a classic IDOR pattern where access control is entirely absent at the object level despite presence at the route level (requiring subscriber authentication). The CVSS vector AC:H suggests the practical exploitation involves an additional hurdle, likely the need to enumerate or predict valid conversation identifiers belonging to other users.

RemediationAI

Update the AI Engine WordPress plugin to version 3.5.5 or later immediately, as a vendor patch is confirmed available. The WPScan advisory at https://wpscan.com/vulnerability/b7825c8a-1817-4a17-b641-076e48ac7c2e/ provides further detail. If an immediate update is not feasible, disabling the discussions feature within the AI Engine plugin settings eliminates the vulnerable code path entirely, though this removes the chatbot conversation persistence functionality as a trade-off. As an additional compensating control on sites with open user registration, temporarily restricting new subscriber registrations reduces the attacker pool until patching is complete. Audit existing conversation logs for anomalous cross-user access patterns if the discussions feature has been active on an unpatched installation.