Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain contributor-level account
-
ExploitConfigure/run WPeMatico feed campaign
-
ExecutionBypass publish + authorship checks
-
ImpactPublish live posts attributed to administrator
Vulnerability Assessment
| Weakness |
CWE
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation 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 WordPress account with contributor-level role or above on a site running the WPeMatico RSS Feed Fetcher plugin before 2.8.27; the attacker then runs a feed campaign, which fails to verify publish permission or author attribution. Limiting factors: the site must have this specific plugin installed, the attacker must possess a valid low-privilege account (not fully unauthenticated), and impact is confined to content publishing and author spoofing - no code execution, data disclosure, or availability loss. No special non-default configuration is required beyond having the plugin active and the feed-campaign feature usable by contributors. |
| Impact | This is a moderate-severity, low-priority authorization flaw. The vendor CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N = 4.9) rates it Medium, but the metric choices are internally inconsistent: the description states the attacker only needs contributor-level access, which is a low-privilege role in WordPress, so PR:H overstates the barrier (PR:L is more accurate) while I:H overstates the impact (publishing posts and spoofing authorship is bounded content integrity, not full system integrity - closer to I:L). These roughly offset. All exploitation signals point to low real-world urgency: EPSS is 0.13% (2nd percentile), SSVC scores Exploitation=none, Automatable=no, and Technical Impact=partial, and there is no CISA KEV listing. A public WPScan proof-of-concept exists, but POC availability is not active exploitation. Confidentiality and availability are unaffected (C:N/A:N); the flaw is purely an integrity/authorization issue. Net: a legitimate but low-priority bug - patch during normal cycles. |
| Exploit ScenarioDerived | An attacker who already holds (or obtains via self-registration/social engineering) a contributor account on a WordPress site running WPeMatico configures or triggers a feed campaign that publishes posts live and sets an administrator as the post author, bypassing the contributor's normal draft-only, own-authorship restrictions. This lets a low-privilege user push published content attributed to a trusted admin (defacement, misattribution, or planting content under an authoritative identity). A public proof-of-concept is available from WPScan. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 28, 2026
Authenticated contributors can bypass publishing permissions and spoof post authorship in WordPress sites running WPeMatico RSS Feed Fetcher before 2.8.27. By running a feed campaign, a user with contributor-level access or above can publish posts live without editorial review and set any registered user, including an administrator, as the author. Publicly available exploit code exists, but no active exploitation has been reported, and the EPSS score is low at 0.13% (percentile 2%). The independent assessment rates this as a moderate-severity, low-priority authorization flaw.
RemediationAI
Upgrade the WPeMatico RSS Feed Fetcher plugin to version 2.8.27 or later to address the authorization flaw. This is the vendor-released patch and is the primary remediation. If immediate patching is not possible, mitigate the risk by restricting the contributor role or reviewing user accounts: remove contributor-level access from untrusted users, or use a role-management plugin to explicitly deny the publish_posts capability to contributors. Note that such restrictions may prevent legitimate contributors from publishing content via feed campaigns. Additionally, monitor for unexpected posts or author changes. Vendor advisory: https://wpscan.com/vulnerability/829bfdc3-7a15-4d6a-9782-72d34fd114b7/.
Affected VersionsENISA
Affected Packages
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 vulnerability resides in the WPeMatico RSS Feed Fetcher plugin for WordPress, specifically in its feed campaign functionality. The plugin fails to perform authorization checks when a user runs a feed campaign, allowing a contributor-level user to publish posts and assign authorship arbitrarily. This is an instance of CWE-269 (Improper Privilege Management), where the plugin does not verify that the user has the publish_posts capability or that they are permitted to set the post author to another account. WordPress role and capability systems are bypassed, leading to a privilege escalation that compromises content integrity but not confidentiality or availability. The affected product is identified by CPE cpe:2.3:a:unknown:wpematico_rss_feed_fetcher:*:*:*:*:*:*:*:* for versions before 2.8.27.
Know when Wpematico Rss Feed Fetcher 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
AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
Contributor is a low-privilege authenticated role so PR:L (not PR:H); impact is bounded content-integrity/author-spoofing so I:L, with no confidentiality or availability effect.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The WPeMatico RSS Feed Fetcher WordPress plugin before 2.8.27 does not verify that a user running a feed campaign is permitted to publish content or to attribute posts to another account, allowing users with contributor-level access and above to publish posts live and set any registered user, including an administrator, as the post author.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
More in Wpematico Rss Feed Fetcher
View allPrivilege escalation in WPeMatico RSS Feed Fetcher (all versions through 2.8.24) allows any authenticated WordPress subs
Stored cross-site scripting in the WPeMatico RSS Feed Fetcher WordPress plugin before 2.8.27 lets an authenticated user
Stored cross-site scripting in the WPeMatico RSS Feed Fetcher WordPress plugin before 2.8.26 allows authenticated users
Stored cross-site scripting in the WPeMatico RSS Feed Fetcher WordPress plugin before version 2.8.26 allows authenticate
The WPeMatico RSS Feed Fetcher WordPress plugin before 2.6.12 does not escape the Feed URL added to a campaign before ou
Server-side request forgery in the WPeMatico RSS Feed Fetcher WordPress plugin before 2.8.27 lets an authenticated user
Server-side request forgery in the WPeMatico RSS Feed Fetcher WordPress plugin before version 2.8.27 allows an authentic
Stored/reflected Cross-Site Scripting in the WPeMatico RSS Feed Fetcher WordPress plugin (versions 2.8.17 and earlier) a
Authenticated information disclosure in the WPeMatico RSS Feed Fetcher WordPress plugin before 2.8.26 lets any account w
Stored cross-site scripting in the WPeMatico RSS Feed Fetcher WordPress plugin (etruel) affects all versions up to and i
EUVD-2026-87893
GHSA-m259-ww4h-6j9q
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB