CVE-2022-29451
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 · uneditedCross-Site Request Forgery (CSRF) leading to Arbitrary File Upload vulnerability in Rara One Click Demo Import plugin <= 1.2.9 on WordPress allows attackers to trick logged-in admin users into uploading dangerous files into /wp-content/uploads/ directory.
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 confidenceThe Rara One Click Demo Import plugin <= 1.2.9 contains a CSRF vulnerability that allows attackers to forge requests and trick authenticated administrators into uploading arbitrary files to the /wp-content/uploads/ directory. This bypasses normal upload restrictions by exploiting the lack of anti-CSRF tokens in the upload functionality.
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< 1.3.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 plugin installationCheck if the Rara One Click Demo Import plugin is installed in your WordPress site. In the WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Rara One Click Demo Import' by Rarathemes. Alternatively, check if the directory /wp-content/plugins/rara-one-click-demo-import/ exists on your server.Affected if The plugin is installed and active on the WordPress site
-
Identify installed versionIn the WordPress admin under Plugins > Installed Plugins, find the Rara One Click Demo Import plugin and note the version number displayed. Compare this version against the affected range of versions less than 1.3.0.Affected if The installed version is 1.2.9 or lower (any version below 1.3.0)
-
Confirm demo import feature is accessibleLog in as an administrator and navigate to the plugin's demo import page, typically found under Appearance > Import Demo Data or a similar menu item provided by the plugin. Verify the import functionality page loads and is accessible.Affected if The demo import feature is accessible and functional in the admin dashboard
-
Check upload directory permissionsVerify that the /wp-content/uploads/ directory is writable by the web server. This can be checked via file permissions on the server (typically 755 or 775 for the directory) or through hosting control panel file managers.Affected if The uploads directory is writable, allowing the plugin's upload function to write files
You are affected if the Rara One Click Demo Import plugin is installed with version 1.2.9 or lower and the demo import functionality is active and accessible to administrators.
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 · scoped1.3.0
Update the Rara One Click Demo Import plugin to the latest version (1.2.10 or higher) which includes CSRF protection, or disable the plugin if not needed. Additionally, enforce SameSite cookies and implement anti-CSRF tokens in custom plugin code.
1.3.0 or later
- Backup your WordPress site before making any changes
- Update the Rara One Click Demo Import plugin to version 1.3.0 or later through the WordPress admin dashboard under Plugins > Installed Plugins
- Alternatively, download the latest version from wordpress.org and upload it manually
- Verify the update was successfully applied by checking the plugin version in Plugins > Installed Plugins
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29451 — 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-29451 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