Unrestricted File UploadWeakness · CWE-434

CVE-2025-46490

CRITICAL · 9.9 CVSS v3.1 Published 2025-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Unrestricted Upload of File with Dangerous Type vulnerability in wordwebsoftware Crossword Compiler Puzzles crossword-compiler-puzzles allows Upload a Web Shell to a Web Server.This issue affects Crossword Compiler Puzzles: from n/a through <= 5.2.

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 confidence

Unrestricted file upload vulnerability in Crossword Compiler Puzzles allows attackers to upload dangerous file types (web shells) directly to the web server. With a CVSS 9.9 rating, successful exploitation enables complete remote code execution on the affected system.

MitigationImplement strict allowlist-based file type validation, store uploads outside the webroot, disable script execution in upload directories, and update to a patched version once released by wordwebsoftware.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Crossword Compiler Puzzles installation
    Locate the web application directory or check running web services for 'crossword' or 'wordwebsoftware' components
    Affected if Crossword Compiler Puzzles is installed and accessible via web
  2. Determine installed version
    Check application files for version information (typically in about.php, version.txt, or the main executable/dll properties)
    Affected if Version matches or precedes the range containing CVE-2025-46490 (contact vendor for exact version numbers)
  3. Verify upload functionality is exposed
    Access the puzzle upload or file upload endpoint in the web interface
    Affected if The upload feature is accessible without authentication or with low-privilege access
  4. Inspect upload directory location
    Check web server configuration and application settings for the upload path; verify if uploads are stored within the webroot
    Affected if Upload directory is inside the publicly accessible web root
  5. Check file type validation configuration
    Review application configuration files or source code for allowed file type restrictions on uploads
    Affected if No strict allowlist validation exists, or dangerous extensions (php, asp, jsp, exe) are permitted

User is affected if Crossword Compiler Puzzles is running with an unpatched version and the upload feature is accessible from the web without proper file type restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based file type validation, store uploads outside the webroot, disable script execution in upload directories, and update to a patched version once released by wordwebsoftware.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46490 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-46490 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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