Wpvivid Backup For MainwpWordPress extension · Wpvivid
CVE-2024-35664
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpvividplugins WPvivid Backup for MainWP wpvivid-backup-mainwp allows Reflected XSS.This issue affects WPvivid Backup for MainWP: from n/a through <= 0.9.32.
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 confidenceReflected XSS vulnerability in WPvivid Backup for MainWP plugin allows injection of malicious scripts through unneutralized user input during web page generation. The vulnerability exists in versions up to and including 0.9.32.
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
Wpvivid Backup For MainwpWordPress extension
< 0.9.33CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Check if WPvivid Backup for MainWP is installedNavigate to WordPress Admin > Plugins > Installed Plugins and look for 'WPvivid Backup for MainWP' in the list, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' and check for 'wpvivid-backup-mainwp'Affected if The plugin is listed in the installed plugins
If the plugin is installed and the version is 0.9.32 or lower, the environment is vulnerable to the reflected XSS described in this CVE.
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.33
Update WPvivid Backup for MainWP to a version beyond 0.9.32 that contains the security patch, or implement proper input validation and output encoding in the vulnerable code paths.
0.9.33
- 1. Log in to the WordPress admin dashboard where the MainWP child plugin is installed.
- 2. Navigate to Plugins > Installed Plugins.
- 3. Locate 'WPvivid Backup for MainWP' in the plugin list.
- 4. Check if an update is available. If not, verify the current version is below 0.9.33.
- 5. If an update is available, click 'Update Now' to upgrade to version 0.9.33 or later.
- 6. Alternatively, you can manually download version 0.9.33 or latest from the WordPress plugin repository and reinstall.
- 7. After updating, verify the plugin version is 0.9.33 or higher to confirm the fix is applied.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wpvivid Backup For Mainwp
Scoped from the published advisory
- 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-2024-35664 — 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-2024-35664 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