CVE-2024-31292
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in Moove Agency Import XML and RSS Feeds.This issue affects Import XML and RSS Feeds: from n/a through 2.1.5.
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 Moove Agency Import XML and RSS Feeds WordPress plugin (versions up to 2.1.5) contains an unrestricted file upload vulnerability allowing attackers to upload dangerous file types without proper validation. This could enable remote code execution if malicious executable files (such as PHP scripts) are uploaded and subsequently accessed.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 the plugin is installedCheck your WordPress installation for the Moove Agency Import XML and RSS Feeds plugin in wp-content/plugins/ or via the WordPress admin Plugins pageAffected if The plugin appears in your installed plugins list
-
Determine the installed plugin versionLocate the main plugin file (typically moove-agency-import-xml-rss-feeds.php) and check the version header comment, or view the version in WordPress admin plugin detailsAffected if The version is 2.1.5 or lower
-
Identify the upload functionalityLook for the file upload form or endpoint in the plugin settings - typically found under the plugin admin menu where feeds are importedAffected if The plugin provides a file upload interface for importing XML, RSS, or CSV feeds
-
Locate the upload directoryCheck wp-content/uploads/ or the configured upload directory for files uploaded by this plugin; inspect directory listing for unexpected file typesAffected if The directory contains executable files (PHP, .phtml, .exe) or file types beyond XML and CSV
-
Review web server access logs for upload activitySearch access logs for POST requests to the plugin upload endpoint, looking for requests uploading files with dangerous extensionsAffected if Logs show upload attempts for .php, .phtml, or other executable extensions to the plugin upload handler
Your environment is likely affected if the Moove Agency Import XML and RSS Feeds plugin version is 2.1.5 or lower and the upload feature is accessible or has been used.
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.
From vendor dataUpdate the plugin to the latest version which implements proper file type validation, restricts allowed upload extensions to safe types only (e.g., XML, CSV), and stores uploads outside the web root or applies strict access controls.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31292 — 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-31292 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