Skip to main content

WP Plugin Info Card CVE-2026-62127

| EUVDEUVD-2026-94888 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-08 audit@patchstack.com GHSA-wxrg-6rfg-7hw8
6.5
CVSS 3.1 · Vendor: patchstack
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privileged WP account
  2. Delivery
    Inject stored XSS payload via plugin field
  3. Exploit
    Payload persisted in plugin info card
  4. Execution
    Admin/user renders affected page
  5. Persist
    Script executes in victim browser session
  6. Impact
    Hijack session or perform privileged actions

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

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 WordPress user with at least low-level posting/content privileges (PR:L) to store the malicious payload in a field handled by the WP Plugin Info Card plugin, plus a separate victim (typically an administrator or another user) who must subsequently view the page rendering the plugin info card (UI:R). These two factors - prior authenticated access and required victim interaction - are the primary limiting conditions; the flaw is not exploitable by fully unauthenticated attackers and is not triggered automatically. It affects WP Plugin Info Card versions from the earliest through 6.3.5. No non-default configuration appears necessary beyond having the plugin installed and active.

Impact

This is a moderate-risk, authenticated Stored XSS (CWE-79) in the WP Plugin Info Card WordPress plugin, with a vendor-assigned CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L). The vector is consistent and internally coherent for a stored XSS: network-reachable (AV:N), low attack complexity (AC:L), but it requires an authenticated contributor-level account (PR:L) AND a victim to render the injected page (UI:R), with a changed scope (S:C) reflecting execution in the victim's browser context. No EPSS score, KEV listing, or public POC is present in the provided data, so the only exploitation signal is the CVSS vector itself - exploitation probability cannot be quantified from this input. There is no conflict between signals, but the real-world priority is tempered by the two hard gating requirements (prior authenticated access plus user interaction), which make this far less urgent than an unauthenticated RCE despite the 'network' attack vector. Treat as a standard patch-cycle item rather than an emergency: a credentialed low-privilege insider or a compromised contributor account is the realistic threat model, not mass internet-wide exploitation.

Exploit ScenarioDerived

An attacker with a low-privileged authenticated WordPress account (e.g., contributor or author) injects a malicious script payload into a field rendered by the WP Plugin Info Card plugin, which is stored persistently. When an administrator or other user later views the page containing the plugin info card, the script executes in their browser session, potentially stealing session cookies or performing actions as that user. No public exploit code was identified in the provided data, so exploitation currently requires an attacker to develop the payload independently.

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 08, 2026

Stored cross-site scripting in the WordPress plugin WP Plugin Info Card (all versions through 6.3.5) lets an authenticated user with low-level posting privileges place a malicious script into content that the plugin later renders as an info card, so the payload executes in the browser of any user who views the affected page. Successful exploitation requires two separate conditions: the attacker must already hold a WordPress account able to create or edit the relevant content (PR:L), and a victim - typically an administrator or another site user - must subsequently view the rendered card (UI:R); the flaw is not reachable by fully unauthenticated attackers and does not fire automatically. Patchstack rates it CVSS 6.5, and there is no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, so the practical exposure is limited to sites running the plugin with multiple content-authoring accounts.

RemediationAI

Patch status: no vendor-released patch identified at time of analysis - the input supplies no fixed version, commit, or pull request, only the Patchstack advisory for 6.3.5, so do not assume any specific 6.3.x version is clean. Until MediaRon publishes a fixed release, the most direct compensating control is to deactivate or uninstall WP Plugin Info Card (the trade-off is loss of the plugin info card rendering feature on all pages and posts), and to remove or replace any existing shortcode blocks that reference it so stored payloads are no longer emitted. Because exploitation requires a low-privilege authenticated account, a second practical mitigation is to tighten authoring roles: audit users with Contributor/Author/Editor capabilities, remove dormant or untrusted accounts, and avoid granting content-creation privileges to parties who do not need them - this reduces but does not eliminate risk, since any content author remains a valid vector. Sites that must keep the plugin active should add a Content-Security-Policy header that disallows inline and third-party script execution (side effect: it may break other front-end scripts and requires careful rollout), and should review recently created or edited posts containing plugin-info-card shortcodes for injected script tags and clean them manually. Monitor the Patchstack advisory page https://patchstack.com/database/wordpress/plugin/wp-plugin-info-card/vulnerability/wordpress-wp-plugin-info-card-plugin-6-3-5-cross-site-scripting-xss-vulnerability?_s_id=cve and the WordPress plugin directory for a patched version, and apply it as soon as it is released; after upgrading, re-scan stored content, since patching the plugin stops new injections but does not automatically purge already-persisted payloads.

Affected VersionsENISA

WP Plugin Info Card 0 ≤6.3.5

Affected Packages

euvd wp_plugin_info_card 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-79, improper neutralization of input during web page generation, in the WordPress plugin WP Plugin Info Card, which builds HTML cards that display metadata from WordPress.org plugin/theme repositories and from user-supplied card attributes. Because the plugin assembles markup from stored input without adequate escaping or context-aware sanitization, attacker-controlled content persists in the database and is later emitted into the page, making this a stored (persistent) rather than reflected XSS variant. The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L indicates the attack is delivered over the network with low complexity, requires a prior authenticated low-privilege account, and additionally requires victim interaction; the scope change (S:C) reflects that the injected script runs in the victim's browser context and can act beyond the vulnerable component, for example performing actions as the viewing user. The WordPress/plugin ecosystem context - a third-party plugin installed on a CMS where administrators frequently preview and view front-end pages containing shortcode-rendered content - is what turns a low-privilege content-authoring account into the initial foothold. No CPE strings were supplied in the input; the affected product identity comes from the EUVD record (EUVD-2026-94888) and the Patchstack advisory covering WP Plugin Info Card up to and including 6.3.5.

Know when Wordpress Plugin 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 6.5 MEDIUM
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
vuln.today AI 6.5 MEDIUM

Stored XSS requires a low-privileged authenticated account to inject (PR:L) and a victim to render the page (UI:R); scope changes to the victim browser (S:C) with limited C/I/A impact.

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

Primary rating from Vendor (patchstack).

CVSS VectorVendor: patchstack

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

DescriptionCVE.org

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in MediaRon LLC WP Plugin Info Card wp-plugin-info-card allows Stored XSS.This issue affects WP Plugin Info Card: from n/a through 6.3.5.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Low
niche WordPress plugin for displaying plugin info cards, limited install base
Data Quality
5 sources
Confidence: Medium

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 No
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

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

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

CVE-2024-50498 CRITICAL POC
10.0 Oct 28

Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u

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