What is the CVSS score of EUVD-2025-20877?

EUVD-2025-20877 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 32.5%.

Which versions of Events Manager are affected by EUVD-2025-20877?

Organizations using all face notable risk from CVE-2025-6970, a SQL injection vulnerability rated CVSS 7.5.. A patch is available.

Is there a public PoC exploit available for EUVD-2025-20877?

Yes, a public proof-of-concept exploit is available for EUVD-2025-20877. Prioritise patching immediately. EPSS: 32.5%.

How to fix or mitigate EUVD-2025-20877?

Within 24 hours: Identify all affected systems running all and apply vendor patches immediately. Validate that input sanitization is in place for all user-controlled parameters.

Events Manager EUVD-2025-20877

| CVE-2025-6970 HIGH

SQL Injection (CWE-89)

2025-07-09 security@wordfence.com

WordPress SQLi Events Manager PHP

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

EUVD ID Assigned

Mar 16, 2026 - 06:20 euvd

EUVD-2025-20877

Analysis Generated

Mar 16, 2026 - 06:20 vuln.today

Patch released

Mar 16, 2026 - 06:20 nvd

Patch available

CVE Published

Jul 09, 2025 - 23:15 nvd

HIGH 7.5

DescriptionCVE.org

The Events Manager - Calendar, Bookings, Tickets, and more! plugin for WordPress is vulnerable to time-based SQL Injection via the ‘orderby’ parameter in all versions up to, and including, 7.0.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Analysis

Technical ContextAI

SQL injection occurs when user-supplied input is incorporated into SQL queries without proper sanitization or parameterized queries.

RemediationAI

A vendor patch is available — apply it immediately. Use parameterized queries or prepared statements. Apply input validation and escape special characters. Implement least-privilege database accounts.