CVE-2025-3917
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 · uneditedThe 百度站长SEO合集(支持百度/神马/Bing/头条推送) plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the download_remote_image_to_media_library function in all versions up to, and including, 2.0.6. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 Baidu SEO collection WordPress plugin fails to validate file types in the download_remote_image_to_media_library function, allowing unauthenticated attackers to upload arbitrary files to the server. This arbitrary file upload vulnerability with CVSS 9.8 creates a direct path 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 Baidu SEO collection plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Baidu SEO collection' or check the plugin files in wp-content/plugins/baidu-seo-collectionAffected if plugin is present and active
-
Check installed plugin versionView the plugin main file (usually index.php or main php file in the plugin directory) and look for the Version header in the plugin comment block, or check the version in WordPress admin plugin listAffected if version is 2.0.6 or lower (any version up to 2.0.6)
-
Inspect upload directory for suspicious filesCheck wp-content/uploads and subdirectories for files with unexpected extensions such as .php, .phtml, .php5, .php7, .jpg.php, or other executable file types that were not intentionally uploadedAffected if unexpected script files exist in upload directories
-
Review access logs for file upload requestsExamine web server access logs (Apache/nginx) for POST requests to the plugin endpoint containing 'download_remote_image_to_media_library' or unusual upload activity targeting the pluginAffected if log entries show POST requests to the vulnerable function with file upload attempts
User is affected if the Baidu SEO collection plugin is installed with any version up to and including 2.0.6, or if suspicious executable files appear in upload directories indicating exploitation
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 dataImmediately disable or remove the affected plugin (versions up to 2.0.6) until a patched version is available; if the plugin must remain in use, implement WAF rules to block unauthorized file upload requests to the vulnerable endpoint.
- 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-2025-3917 — 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-2025-3917 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