CVE-2021-47933
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWordPress MStore API 2.0.6 contains an arbitrary file upload vulnerability that allows unauthenticated attackers to upload malicious files by sending POST requests to the REST API endpoint. Attackers can upload PHP files with arbitrary names to the config_file endpoint to achieve remote code execution on the server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWordPress MStore API plugin 2.0.6 contains an unauthenticated arbitrary file upload vulnerability in the REST API config_file endpoint, allowing attackers to upload PHP files with arbitrary filenames leading to remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify MStore API plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'MStore API' or check the plugin files in /wp-content/plugins/ directory for the mstore-api folderAffected if MStore API plugin is present and active on the WordPress site
-
Check installed MStore API versionIn WordPress admin, view the plugin details page for MStore API to see the version number, or check the main plugin file (usually index.php or mstore-api.php) for the version headerAffected if The installed version is 2.0.6 or earlier (any version prior to patched release)
-
Test config_file REST API endpoint accessibilitySend a GET request to /wp-json/mstore/v1/config_file or /wp-json/ and look for the 'config_file' endpoint in the available routesAffected if The config_file endpoint is registered and responds to requests (indicating the vulnerable endpoint is active)
-
Check for suspicious uploaded files in wp-contentInspect the /uploads/ directory (especially /uploads/ and any custom upload paths) for recently created .php files with random or suspicious namesAffected if Unexpected PHP files exist in upload directories, especially those not created by legitimate site administrators
A WordPress site is affected if the MStore API plugin version 2.0.6 or earlier is installed and the vulnerable config_file REST API endpoint is exposed and accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImmediately update to a patched version of MStore API, or disable the config_file REST API endpoint and block unauthenticated API access until a patch is available.
MStore API latest version (2.0.7 or higher)
- 1. Update MStore API plugin to the latest available version from the WordPress plugin repository
- 2. If an update is not available, immediately deactivate the MStore API plugin
- 3. Audit the WordPress installation for any newly uploaded malicious files in the wp-content/uploads/ directory
- 4. Review WordPress user accounts for any unauthorized administrative accounts
- 5. If exploitation is suspected, restore from a clean backup prior to the vulnerability disclosure
- 6. Implement web server-level access controls to restrict API endpoint access to authenticated users only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-47933 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-47933 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data