Skip to main content

Ultimeter EUVDEUVD-2026-85502

| CVE-2026-95593 HIGH
SQL Injection (CWE-89)
2026-09-23 Patchstack GHSA-2f7w-8mhv-m9fx
7.6
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain high-privileged WP account
  2. Delivery
    Access Ultimeter editor endpoint
  3. Exploit
    Inject SQL via crafted parameter
  4. Execution
    Query executes in database
  5. Impact
    Exfiltrate sensitive data across scope

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated high-privileged WordPress account (PR:H - consistent with the 'Editor' context in the title, i.e. Editor/Administrator-level access) that can reach the vulnerable Ultimeter editor functionality; the affected plugin versions are Ultimeter <= 3.0.8. No user interaction is needed (UI:N) and the attack is network-reachable (AV:N) with low complexity (AC:L). The primary limiting factor is the privilege requirement: an ordinary or unauthenticated visitor cannot trigger it, so realistic risk is confined to malicious insiders or attackers who have already taken over a privileged account. Deployment is limited to WordPress sites running this specific plugin at or below version 3.0.8.

Impact

This is an authenticated SQL injection (CWE-89) in the WordPress plugin Ultimeter (<= 3.0.8), reported by Patchstack. The provided CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L (score 7.6) indicates a network-reachable, low-complexity attack requiring high privileges (PR:H) and no user interaction, with a scope change (S:C), full confidentiality impact (C:H), no integrity impact (I:N), and low availability impact (A:L). The PR:H requirement is the dominant limiting factor: an attacker must already hold a high-privileged role (the 'Editor' context named in the title implies an authenticated back-end user), which sharply narrows the realistic threat to insiders or attackers who have already compromised a privileged account. Exploitation status is: no public exploit identified at time of analysis - there is no EPSS score, no CISA KEV listing, and no POC referenced in the single Patchstack advisory. There is no SSVC decision data provided. In practical terms this is a moderate, not urgent, issue: the CVSS of 7.6 is elevated mainly by S:C and C:H, but the PR:H gate and the niche footprint of the plugin make widespread opportunistic exploitation unlikely. The C:N-for-integrity but A:L pattern is consistent with a read-oriented SQLi that can also degrade availability (e.g., heavy/blind queries). No conflicting signals between the vector and description were identified; both point to authenticated network exploitation.

Exploit ScenarioDerived

An attacker who holds (or has phished/compromised) a high-privileged WordPress account such as Editor/Administrator submits a crafted parameter to a vulnerable Ultimeter editor endpoint, injecting SQL into a back-end query. This lets them read arbitrary database contents (user records, password hashes, secrets) beyond their intended scope. No public POC or exploit code is currently referenced in the advisory.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 23, 2026

Authenticated SQL injection in the WordPress plugin Ultimeter (versions through 3.0.8) lets a high-privileged account - Editor or Administrator level - inject arbitrary SQL through the plugin's editor functionality, exposing data held in the site's WordPress database. The flaw is scored CVSS 3.1 7.6 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L), where the changed scope and high confidentiality impact reflect that the database is a security authority separate from the vulnerable plugin. No public exploit identified at time of analysis; because the vector requires PR:H, realistic risk is confined to malicious insiders or attackers who have already taken over a privileged WordPress account on a site running the affected plugin version.

RemediationAI

No vendor-released patch version is confirmed in the supplied intelligence at the time of analysis, so the first step is to check the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/ultimeter/vulnerability/wordpress-ultimeter-plugin-3-0-8-sql-injection-vulnerability) for a fixed Ultimeter release and, if one is listed, upgrade the plugin immediately to that version; if the plugin is no longer maintained, treat it as unsupported software. Where no patch can be applied, the most effective compensating control is removing the privilege path the attack depends on: deactivate the Ultimeter plugin if its polls/rating functionality is not business-critical (side effect: loss of that feature on the site), or, if it must stay active, audit and reduce who holds Editor and Administrator roles and strip unnecessary capabilities from Editor accounts so untrusted users cannot reach the vulnerable editor functionality (side effect: workflow and content-management disruption for legitimate editors). Because the exploit vector is a network request carrying SQL syntax, a WAF or reverse proxy with SQL-injection signatures rules can block common payloads in front of wp-admin, though obfuscated queries may bypass signature-based rules. Finally, since confidentiality impact is high and the injection reads from the database, treat any site where an untrusted user has held Editor-level access as potentially compromised: rotate WordPress salts and privileged account passwords, review database and admin activity logs for anomalous queries, and scan for injected content or exfiltration attempts. Do not rely on deactivating the plugin alone to retroactively undo already-performed data reads.

Affected VersionsENISA

Ultimeter n/a ≤3.0.8

Affected Packages

euvd ultimeter no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-89, improper neutralization of special elements used in an SQL command, in the editor-facing functionality of the Ultimeter WordPress plugin. Rather than passing user-supplied input through WordPress's prepared-statement API ($wpdb->prepare) with properly bound parameters, the affected code builds a SQL query with unescaped input, allowing SQL syntax to be injected into the query executed against the site's MySQL/MariaDB database. The CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L) describes a network-reachable, low-complexity attack that requires an authenticated account with high privileges (consistent with the 'Editor' wording in the CVE title, i.e. WordPress Editor or Administrator capability) and needs no user interaction. The S:C scope change indicates the impact crosses a trust boundary from the plugin into the underlying database, while C:H reflects full read exposure of database contents and I:N/A:L indicate no confirmed integrity impact and only limited availability impact - this is primarily a data-disclosure primitive (e.g. extraction of user credentials hashes, configuration, or other plugin tables) rather than a code-execution or destructive primitive. The CPE namespace cpe:2.3:a:ben_roberts:ultimeter identifies the vendor as Ben Roberts and the product as the WordPress plugin Ultimeter; ENISA's EUVD entry EUVD-2026-85502 mirrors the affected range. No public exploit or CISA KEV listing is present in the supplied intelligence.

Know when Ultimeter gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.6 HIGH
AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 7.6 HIGH

Network-reachable authenticated SQLi requiring a high-privileged role (PR:H); scope change and full DB read give S:C/C:H, no integrity impact, minor availability impact from query load.

3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

DescriptionCVE.org

Editor SQL Injection in Ultimeter <= 3.0.8 versions.

Executive ViewAI

Why It Matters

Sites running the WordPress Ultimeter plugin through version 3.0.8 face a high-severity database data-exposure risk because an already privileged Editor or Administrator account can retrieve information from the site's WordPress database. No public exploit identified at time of analysis, so the practical threat is limited to malicious insiders or attackers who have already compromised a privileged WordPress account. Leadership should care because these roles often exist for content operations, and excessive or unmonitored privileged access could turn a single account takeover into unauthorized disclosure of site data. No vendor-released patch identified at time of analysis.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include deactivating or removing the Ultimeter plugin where feasible, restricting Editor/Administrator roles, enforcing least privilege and MFA, auditing privileged WordPress accounts, monitoring database activity, and deploying WAF/virtual patching rules to detect SQL injection on the plugin's editor functionality.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Low
niche WordPress fundraising-meter plugin, limited install base
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy