dbcve.org
WiclearApplication

CVE-2007-1097

HIGH · 10.0 CVSS v2.0 Published 2007-02-26
Fix available
A fix is available. Upgrade to after 0.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 file upload vulnerability in the onAttachFiles function in the upload tool (inc/lib/attachment.lib.php) in Wiclear before 0.11.1 allows remote attackers to upload and execute arbitrary PHP code via unspecified vectors related to filename validation. NOTE: some details were obtained from third party information.

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

Wiclear before 0.11.1 contains an unrestricted file upload vulnerability in the onAttachFiles function within inc/lib/attachment.lib.php. The application fails to properly validate filenames, allowing remote attackers to upload malicious PHP files and execute arbitrary code on the server.

MitigationUpgrade to Wiclear 0.11.1 or later. Until patched, disable the file upload functionality or implement strict whitelist-based file type and filename validation in attachment.lib.php.

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
WiclearApplication
Affected:<= 0.11

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 Wiclear installation version
    Locate the version file or index.php in the Wiclear web root and check the declared version number (typically in a version.php file, config, or the main index page)
    Affected if The installed version is 0.11 or any version lower than 0.11.1
  2. Verify vulnerable file exists
    Check for the presence of inc/lib/attachment.lib.php in the web root directory
    Affected if The file inc/lib/attachment.lib.php exists and contains the onAttachFiles function
  3. Confirm file upload functionality is enabled
    Review the Wiclear configuration settings or database for the file upload feature flag; attempt to access the file upload interface/page
    Affected if File upload functionality is enabled and accessible to users
  4. Check upload directory accessibility
    Identify the upload directory (commonly uploads/ or attachments/) and verify it is web-accessible and writable
    Affected if The upload directory is writable and accessible via the web server
  5. Inspect onAttachFiles function for filename validation
    Open inc/lib/attachment.lib.php and locate the onAttachFiles function; examine the code for file type or extension validation logic
    Affected if The function lacks proper file extension or MIME type validation (no whitelist checking for .php or other executable extensions)

A user is affected if running Wiclear version 0.11 or earlier with the file upload feature enabled and the vulnerable onAttachFiles function present without proper filename validation.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.11
Interim mitigation

Upgrade to Wiclear 0.11.1 or later. Until patched, disable the file upload functionality or implement strict whitelist-based file type and filename validation in attachment.lib.php.

Recommended fix Moderate confidence

Wiclear 0.11.1

  1. 1. Backup your current Wiclear installation and database before making any changes.
  2. 2. Download Wiclear version 0.11.1 or later from the official project repository.
  3. 3. Replace the existing installation files with the new version, preserving your configuration and data files.
  4. 4. Verify that the upload functionality in inc/lib/attachment.lib.php now properly validates file types and names.
  5. 5. Test that the upload feature works correctly with allowed file types.
  6. 6. Confirm that PHP files cannot be uploaded through the attachment upload mechanism.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wiclear Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-1097 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2007-1097 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