WP Plugin Info Card <= 6.2.0 - Cross-Site Request Forgery to Arbitrary Custom Plugin Entry Creation
Strategic Overview
- Status
- Patched in 6.3.0
- Affected Plugin
- WP Plugin Info Card
- Affected Version
<= 6.2.0- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-2023
At a glance
CVE-2026-2023 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Plugin Info Card WordPress plugin, affecting versions <= 6.2.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.3.0; sites on affected versions should update now. Disclosed February 2026, reported by Duong Quang Hao.
Vulnerability Overview
The WP Plugin Info Card plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.2.0. This is due to missing nonce validation in the ajax_save_custom_plugin() function, which is disabled by prefixing the check with 'false &&'. This makes it possible for unauthenticated attackers to create or modify custom plugin entries via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
WP Plugin Info Card <= 6.2.0 carries this weakness at ajax_save_custom_plugin(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP Plugin Info Card the fix is 6.3.0: builds <= 6.2.0 are affected, anything from 6.3.0 onward is not.
Remediation
Update to version 6.3.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Plugin Info Card: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Plugin Info Card 6.3.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C