CVE-2026-121536peterschulznl WP Data Access SQL injection

Low priorityMedium5.3EPSS not scored yet

CVE-2026-121536 is a SQL injection in peterschulznl WP Data Access, rated medium (5.3 on CVSS 3.1).

Why this priority: Medium severity, with no exploitation signal.

Published 7 Nov 2026 · Updated 8 Nov 2026 · NVD status: Deferred

What it is

Input is pasted into a database query, so an attacker can rewrite the query to read or change data.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.

What an attacker gains

A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker read or change records in the data store behind the application.

Is it being exploited?

There is no public report of exploitation yet.

What to do

No fixed version is listed yet. Find every place peterschulznl WP Data Access runs, watch the references for a fix, and plan a replacement if it is no longer supported.
While there is no fix, review who holds accounts that can reach it.

Description from NVD

The WP Data Access – App Builder for Tables, Forms, Dashboards, Charts & Maps plugin for WordPress is vulnerable to generic SQL Injection via the 'engine' parameter in all versions up to, and including, 5.5.90 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is only exploitable when an administrator has configured a Data Project page to admit a lower-privileged role, which is the plugin's documented mechanism for sharing projects with subscribers and other users.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

WordPress sites and their plugins. Plugins run inside the site with its database access, and many sites are public.
Services that build database or directory queries. The flaw sits between the application and its data store.
Databases. The flaw sits between the application and its data store.

Trust boundaries in play

Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
Between the application and its data store. An attacker who crosses it can read or change records in the data store behind the application.

Questions to answer about your own systems

Where does peterschulznl WP Data Access run in your systems, and at which version?
Which of those instances can be reached from the internet or partner networks?
What can it reach once compromised: which data stores, secrets and services?

See how Veriom maps an architecture Take the interactive tour

Advisories

www.wordfence.com/threat-intel/vulnerabilities/id/564eeb3a-13e6-426d-a346-e2d85e88846c?source=cve

Sources

CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.