Atomic Edge analysis of CVE-2026-2023:
This vulnerability is a Cross-Site Request Forgery (CSRF) flaw in the WP Plugin Info Card WordPress plugin, allowing unauthenticated attackers to create or modify custom plugin entries. The issue affects all plugin versions up to and including 6.2.0, with a CVSS score of 4.3. The vulnerability resides in the AJAX handler for saving custom plugin data.
The root cause is the deliberate disabling of nonce verification in the `ajax_save_custom_plugin()` function. In the vulnerable version, the file `wp-plugin-info-card/php/Admin/Init.php` contains a conditional check on line 392 that is prefixed with ‘false &&’. This syntax ensures the `wp_verify_nonce` function is never executed, regardless of the nonce value submitted. The function `ajax_save_custom_plugin` handles POST requests to the `admin-ajax.php` endpoint with the action `wppic_save_custom_plugin`.
Exploitation requires an attacker to trick a logged-in administrator with appropriate capabilities into submitting a forged HTTP request. The attacker crafts a malicious HTML page or link that sends a POST request to `/wp-admin/admin-ajax.php`. The request must include the parameter `action` set to `wppic_save_custom_plugin` and other parameters like `title`, `slug`, and `description` to define the custom plugin entry. Because the nonce check is disabled, the request succeeds if the victim is authenticated, leading to arbitrary data creation or modification.
The patch, applied in version 6.3.0, removes the ‘false &&’ prefix from the nonce verification check on line 392 of `Init.php`. This change activates the `wp_verify_nonce` function, ensuring a valid nonce is required for the request. The patch also updates the plugin version constants in the main plugin file and an asset file. Additionally, the patch introduces new nonce fields (`nonce` and `saveNonce`) in the JSON response for the edit function to facilitate future secure requests.
Successful exploitation allows an attacker to create or overwrite custom plugin entries stored by the plugin. This could lead to data integrity issues, such as injecting malicious links or incorrect metadata into site content that uses the plugin’s display functions. The attack requires social engineering to lure an administrator, but no direct authentication or special privileges are needed from the attacker’s side.







