Premmerce Plugin CVE-2025-64288
MEDIUMAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify target WordPress site running Premmerce ≤1.3.19
-
DeliveryCraft forged HTTP request targeting Premmerce action endpoint
-
ExploitLure authenticated admin to malicious page
-
ExecutionVictim browser submits forged request with session cookie
-
PersistPremmerce processes request without CSRF token validation
-
ImpactUnauthorized state change executed on victim's site
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that a victim user hold an active, authenticated session on the target WordPress site at the moment they visit the attacker's page - an administrator or any user with privileges to invoke the affected Premmerce functionality is the realistic target. The victim must be socially engineered into visiting an attacker-controlled URL or page embedding the forged request (UI:R). The target site must be running Premmerce plugin version 1.3.19 or earlier. No special server configuration or non-default WordPress setting is required beyond having the plugin installed and activated. Exploitation is limited to the integrity impact of actions the authenticated victim is permitted to take; data exfiltration is not possible via CSRF alone. |
| Impact | The CVSS base score of 4.3 (Medium) reflects a restrained integrity-only impact (I:L) with no confidentiality or availability loss, consistent with typical CSRF outcomes such as unauthorized settings changes or content modifications. EPSS at 0.01% places this in the 3rd percentile globally, indicating the security community currently observes virtually no exploitation activity. The vulnerability is absent from the CISA KEV catalog and no public POC or exploit module has been identified. Taken together, these signals suggest this is a real but low-priority finding - the attack requires social engineering to lure an authenticated administrator, limits damage to whatever actions that user could take, and operates in a plugin with limited deployment footprint. The CVSS AC:L metric is technically accurate but somewhat misleading in practice, as successful exploitation still depends on the attacker's ability to deliver a convincing lure to a logged-in admin. |
| Exploit ScenarioDerived | An attacker hosts a webpage containing a hidden HTML form or JavaScript fetch that targets a Premmerce action endpoint on a victim's WordPress site. The attacker sends the link to a WordPress administrator via phishing email or embeds it in a forum post; when the admin loads the page while their WordPress session is active, the browser automatically submits the forged request with the admin's session cookies, performing an unauthorized action within Premmerce's scope. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 25, 2026
Cross-Site Request Forgery in the Premmerce WordPress plugin (versions through 1.3.19) enables network-based attackers to forge state-changing requests on behalf of authenticated WordPress users without their knowledge. The attack succeeds when a logged-in user visits an attacker-controlled page, causing the victim's browser to silently submit a crafted request to their WordPress site. No active exploitation is confirmed (absent from CISA KEV), no public exploit code has been identified, and EPSS sits at 0.01% (3rd percentile), collectively indicating very low real-world exploitation probability at this time.
RemediationAI
Site operators running the Premmerce plugin should update to any version released after 1.3.19 once a patched release is confirmed by the vendor - no specific fixed version is identified in the available source data. As an interim compensating control, administrators can deactivate the Premmerce plugin until a patched version is verified; this eliminates the attack surface with no data-loss risk since CSRF does not exfiltrate data. WordPress-level mitigations such as enforcing HTTPS everywhere and using a Web Application Firewall (WAF) with CSRF rules (e.g., Cloudflare or Wordfence) can reduce exploitation probability but should not be treated as a substitute for patching. Monitor the Patchstack advisory at the reference URL and the WordPress Plugin directory for an updated release.
Affected ProductsAI
The Premmerce plugin for WordPress, versions from the initial release through and including 1.3.19, is confirmed affected per the Patchstack database entry (https://patchstack.com/database/Wordpress/Plugin/premmerce/vulnerability/wordpress-premmerce-plugin-1-3-19-cross-site-request-forgery-csrf-vulnerability). No CPE string was included in the source data. The lower version bound is listed as 'n/a' in the NVD entry, implying all prior releases may be vulnerable. No patch version has been independently confirmed from the available data.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-352 (Cross-Site Request Forgery) describes a class of vulnerabilities where an application processes requests without verifying that the authenticated user intentionally initiated them. In the WordPress ecosystem, plugins are expected to implement nonce-based CSRF protection via wp_nonce_field() on forms and check_admin_referer() or check_ajax_referer() on handlers; absence or improper use of these controls in Premmerce (a WooCommerce enhancement plugin) is the root cause. The CVSS vector AV:N/AC:L confirms the flaw is remotely reachable with no special complexity, and the UI:R component confirms the browser's same-origin cookie behavior is the exploitation mechanism. No CPE string was provided in the source data.
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
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
CSRF inherently requires victim browser interaction (UI:R) and no attacker privileges; integrity-only impact as forged requests cannot read or exfiltrate response data.
Primary rating from NVD.
CVSS VectorNVD
DescriptionCVE.org
Cross-Site Request Forgery (CSRF) vulnerability in Premmerce Premmerce premmerce allows Cross Site Request Forgery.This issue affects Premmerce: from n/a through <= 1.3.19.
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
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB