Migration\, Backup\, StagingWordPress extension · Wpvivid
CVE-2022-27844
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 · uneditedArbitrary File Read vulnerability in WPvivid Team Migration, Backup, Staging – WPvivid (WordPress plugin) versions <= 0.9.70
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 · moderate confidenceThe WPvivid WordPress plugin versions 0.9.70 and below contains an arbitrary file read vulnerability that could allow unauthenticated attackers to read sensitive files on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Migration\, Backup\, StagingWordPress extension
< 0.9.71CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 WPvivid plugin is installedAccess WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'WPvivid' or check the /wp-content/plugins/ directory for wpvivid-backuprestore or similar wpvivid foldersAffected if WPvivid plugin files exist in the WordPress plugins directory
-
Determine installed version numberIn WordPress admin under Plugins > Installed Plugins, locate the WPvivid plugin and read the version number displayed beneath the plugin name, or open the main plugin PHP file and look for the 'Version:' header commentAffected if Version displayed is 0.9.70 or lower (any version below 0.9.71)
-
Confirm plugin is activeCheck the plugin status in WordPress admin - the plugin must be 'Active' not 'Inactive' or 'Must-Use' to be exploitable by unauthenticated attackersAffected if Plugin is activated and processing incoming requests
You are affected if the WPvivid plugin version 0.9.70 or below is installed and active on your WordPress site, allowing unauthenticated attackers to read arbitrary files on the server.
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 · scoped0.9.71
Update the WPvivid plugin to a version newer than 0.9.70. If immediate updating is not possible, deactivate and remove the plugin until the update can be applied.
WPvivid plugin version 0.9.71
- Backup your WordPress site before making any changes
- Navigate to WordPress admin dashboard > Plugins > All Plugins
- Locate WPvivid plugin in the list
- Click 'Update now' when version 0.9.71 is available, or manually upload version 0.9.71 via Plugins > Add New > Upload Plugin
- After updating, verify the plugin shows version 0.9.71 or later in the Plugins list
- Test that the backup/restore functionality works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Migration\, Backup\, Staging
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27844 — 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-2022-27844 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