CVE-2026-9615 json
Flex Import <= 3.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Modification via 'license_activate_fleximp' and 'license_deactivate_fleximp' AJAX Actions
published last mo. modified last mo. also EUVD-2026-83576
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
The Flex Import plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.0. This is due to the license_activate_fleximp() and license_deactivate_fleximp() functions, hooked to the wp_ajax_license_activate_fleximp and wp_ajax_license_deactivate_fleximp AJAX actions, lacking both a capability check (current_user_can()) and nonce verification (the client-side script sends a 'wpnonce' value but the handlers never validate it). This makes it possible for authenticated attackers, with subscriber-level access and above, to activate an arbitrary/fraudulent license key (persisting it via update_option('fleximp_is_premium') and toggling validation, suspension, and bundle status options) or deactivate the site's legitimate license (deleting the stored key and setting fleximp_validation_status to false), thereby disrupting the plugin's premium functionality.
Is CVE-2026-9615 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- flextheme Flex Import
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/0143b789-06ea-47da-9736-3266f91a9e33?source=cve
- plugins.trac.wordpress.org /browser/flex-import/tags/2.8/includes/fleximp-license-functions.php#L86
- plugins.trac.wordpress.org /browser/flex-import/tags/2.8/includes/fleximp-license-functions.php#L93
- plugins.trac.wordpress.org /browser/flex-import/tags/2.8/includes/fleximp-license-functions.php#L159
- plugins.trac.wordpress.org /browser/flex-import/tags/2.8/includes/fleximp-license-functions.php#L161
- plugins.trac.wordpress.org /browser/flex-import/tags/2.5/includes/fleximp-license-functions.php#L86
- plugins.trac.wordpress.org /browser/flex-import/tags/2.5/includes/fleximp-license-functions.php#L93
- plugins.trac.wordpress.org /browser/flex-import/tags/2.5/includes/fleximp-license-functions.php#L159
- plugins.trac.wordpress.org /browser/flex-import/tags/2.5/includes/fleximp-license-functions.php#L161
- plugins.trac.wordpress.org /changeset?reponame=&old=3630901%40flex-import&new=3630901%40flex-import
Sources
- CVE List CVE-2026-9615
- NVD CVE-2026-9615
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.