Skip to main content

paymendo WordPress Plugin CVE-2026-89305

| EUVDEUVD-2026-96792 MEDIUM
SQL Injection (CWE-89)
2026-10-11 WPScan GHSA-cc47-x7cq-5www
6.5
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privilege authenticated account
  2. Exploit
    Submit crafted parameter to vulnerable endpoint
  3. Execution
    Inject SQL into backend query
  4. Impact
    Exfiltrate sensitive database contents

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

Requires an authenticated session with at least a low-privilege account on the target WordPress site (CVSS PR:L); exploitation targets the paymendo plugin (version ≤1.1) where a specific request parameter is passed into a SQL query without proper sanitization/escaping. The exact parameter and endpoint are not named in the available description - confirm against the WPScan advisory. The key limiting factor is the authentication requirement: on sites that disable open user registration, the attacker must first obtain valid credentials, whereas sites allowing self-service subscriber registration effectively reduce this to any attacker. No user interaction is required, and the attack is network-reachable against affected installations.

Impact

This is a moderate-risk, authenticated SQL injection (CWE-89) in the paymendo WordPress plugin. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, 6.5 Medium) indicates network-reachable, low-complexity exploitation that requires some authentication (PR:L) and no user interaction, with high confidentiality impact but no modeled integrity or availability impact. Publicly available exploit code exists (reported by WPScan), which raises practical risk, but there is NO CISA KEV listing and no EPSS score was supplied in the input, so there is no evidence of active or widespread exploitation - POC availability and active exploitation are distinct signals and should not be conflated. The requirement for an authenticated account (PR:L) meaningfully limits the attacker population; however, on WordPress sites that permit open/subscriber-level registration, even the lowest-privileged account can meet this bar, which would effectively lower the barrier. The C:H/I:N/A:N impact profile is plausible for a read-oriented injection but is conservative - real-world SQL injection frequently enables data modification or authentication bypass, so the true integrity/availability impact may be understated; verify the injectable sink against the vendor/WPScan advisory. Net assessment: a real but not emergency priority - patch promptly, prioritizing sites with open registration, but this is not a high-urgency internet-wide threat.

Exploit ScenarioDerived

An attacker registers or obtains any authenticated account on a WordPress site running paymendo ≤1.1, then sends a crafted request with a malicious value in the unsanitized parameter, injecting SQL into the backend query to exfiltrate sensitive database contents such as user credentials or payment-related data. Because low-complexity public exploit code exists (WPScan), weaponization requires little skill; the main constraint is obtaining the required low-privilege account.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 11, 2026

SQL injection in the paymendo WordPress plugin (all versions through 1.1) lets an authenticated user with only low privileges inject arbitrary SQL through a request parameter that is not sanitized or escaped before being placed into a query, exposing database contents to read-out. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, base 6.5) confirms network reachability, no user interaction, and a high confidentiality impact with no integrity or availability effect, and publicly available exploit code exists. The authentication requirement is the key limiting factor: on sites that allow self-service registration, a subscriber account is all that is needed, while closed-registration sites require the attacker to already hold valid credentials.

RemediationAI

No vendor-released patch identified at time of analysis, and the available references contain no fixed version number, so remediation must currently rely on compensating controls rather than an upgrade target. The most effective immediate action is to deactivate and remove the paymendo plugin from any site that does not actively use it; if it is required, isolate the installation behind access controls. Because the attack requires an authenticated session (CVSS PR:L), closing self-service registration and auditing existing low-privilege accounts materially shrinks the attack surface - on sites where open registration cannot be disabled, treat every subscriber account as a potential exploitation vector and review the user list. Deploy WAF or reverse-proxy rules that block SQL metacharacters and UNION/boolean patterns on requests to the plugin's endpoints, accepting that generic SQLi signatures produce false positives on legitimate traffic; a signature tuned to the specific parameter named in the WPScan advisory (https://wpscan.com/vulnerability/072889c7-27c3-4b5a-b5e6-8896b60884a9/) will be more accurate. Additionally, ensure the WordPress database user is scoped to the minimum privileges it needs for normal operation, rotate database credentials and salts if compromise is suspected, and monitor the affected site's database user for anomalous read patterns. Consult https://vuldb.com/vuln/416543 and https://nvd.nist.gov/vuln/detail/CVE-2026-89305 for any vendor fix that may be published after this analysis.

Affected VersionsENISA

paymendo 0 ≤1.1

Affected Packages

euvd paymendo 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

This is a classic SQL injection (CWE-89) in a WordPress plugin. The plugin fails to sanitize and escape an incoming request parameter and then interpolates it directly into a SQL statement instead of using parameterized queries or the WordPress $wpdb->prepare() API. Because WordPress plugins run with the site's database credentials, a successful injection gives the attacker the same read access as the WordPress installation itself, which is why the assessed impact is confidentiality-high rather than scope-changed. The vulnerability was reported by WPScan and is tracked as EUVD-2026-96792 and VulDB 416543, with the WPScan advisory serving as the exploit reference. The affected CPE string (cpe:2.3:a:unknown:paymendo:*:*:*:*:*:*:*:*) uses an unresolved vendor placeholder and a wildcard version, so it cannot be used to narrow down specific builds - the EUVD affected-version data ('paymendo 0 ≤1.1') establishes the upper bound of the vulnerable range as version 1.1. The precise vulnerable parameter and endpoint are not named in the available description and should be confirmed against the WPScan advisory before attempting detection or reproduction.

Know when Paymendo 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 (WPScan) PRIMARY 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 6.5 MEDIUM

Network-reachable injectable parameter (AV:N/AC:L), but any valid account is required so PR:L not PR:N; modeled as read-oriented data disclosure (C:H) with I/A:N per available evidence.

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

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

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

Lifecycle Timeline

3
CVSS changed
Oct 11, 2026 - 12:22 NVD
6.5 (MEDIUM)
CVE Published
Oct 11, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Oct 11, 2026 - 06:00 cve.org
MEDIUM 6.5

DescriptionCVE.org

The paymendo WordPress plugin through 1.1 does not properly sanitize and escape a parameter before using it in a SQL query, allowing any authenticated user to perform SQL injection attacks.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Low
obscure WordPress payment plugin, unknown vendor, early version (≤1.1)
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

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 MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

52
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: +20
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