Skip to content
Fencer Intel
high 7.3

CVE-2023-40004 in the critical feed json

Unauth. Access Token Manipulation vulnerability in multiple ServMask WordPress plugins

published 2y ago modified 5mo ago also EUVD-2023-44627

cvss
7.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
11.0%
EPSS 11.0% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

Missing Authorization vulnerability in ServMask All-in-One WP Migration Box Extension, ServMask All-in-One WP Migration OneDrive Extension, ServMask All-in-One WP Migration Dropbox Extension, ServMask All-in-One WP Migration Google Drive Extension.This issue affects All-in-One WP Migration Box Extension: from n/a through 1.53; All-in-One WP Migration OneDrive Extension: from n/a through 1.66; All-in-One WP Migration Dropbox Extension: from n/a through 3.75; All-in-One WP Migration Google Drive Extension: from n/a through 2.79.

Patch / fix

  • ServMask All-in-One WP Migration Box Extension 1.54
  • ServMask All-in-One WP Migration OneDrive Extension 1.67
  • ServMask All-in-One WP Migration Dropbox Extension 3.76
  • ServMask All-in-One WP Migration Google Drive Extension 2.80

Is CVE-2023-40004 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 Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

10.97% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-21).

CVSS scores

assigned by version score vector
CNA 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected products

  • ServMask All-in-One WP Migration Box Extension
  • ServMask All-in-One WP Migration OneDrive Extension
  • ServMask All-in-One WP Migration Dropbox Extension
  • ServMask All-in-One WP Migration Google Drive Extension
  • servmask all-in-one_wp_migration

Classification

Weakness
Technology feeds

References

Sources

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.