Video Share EnterpriseApplication · Alstrasoft

CVE-2007-2017

HIGH · 7.5 CVSS v2.0 Published 2007-04-12
Fix available
A fix is available. Upgrade to after 4.3 or later.
See remediation →
84/100
Remediation priority · High
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
siteadmin/useredit.php in AlstraSoft Video Share Enterprise does not check authentication, which allows remote attackers to obtain or modify user information via a direct request.

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 confidence

The siteadmin/useredit.php file in AlstraSoft Video Share Enterprise lacks authentication checks, allowing any remote attacker to directly access this administrative function and view, modify, or delete user information without any credentials or session.

MitigationImplement proper authentication and authorization checks on siteadmin/useredit.php to ensure only authenticated administrators can access user modification functions.

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
Video Share EnterpriseApplication
Affected:<= 4.1<= 4.2<= 4.3

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
Partial
Integrity
Partial
Availability
Partial

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

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. Confirm AlstraSoft Video Share Enterprise is installed
    Locate the application installation directory. Common paths may include /var/www/, /htdocs/, or the web root. Look for files containing 'Alstrasoft' or 'Video Share' branding.
    Affected if The software is AlstraSoft Video Share Enterprise
  2. Check the installed version number
    Examine version information in the application, typically found in a README, CHANGELOG, or version file within the installation directory, or check the login/admin page for version disclosure.
    Affected if The version is 4.1, 4.2, 4.3, or any version lower than these
  3. Verify siteadmin/useredit.php exists
    Navigate to the siteadmin/ subdirectory in the web root and confirm that useredit.php file is present.
    Affected if The file siteadmin/useredit.php exists in the installation
  4. Check for authentication on useredit.php
    Access the URL path /siteadmin/useredit.php directly without providing any credentials or session. Inspect the source code of useredit.php to see if it includes any authentication include files (such as include('session.php') or similar) at the beginning.
    Affected if The page loads without requiring login credentials, or the PHP code shows no authentication include files at the start of the script

The environment is affected if AlstraSoft Video Share Enterprise version 4.3 or lower is installed and the siteadmin/useredit.php file is accessible without authentication.

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
Upgrade available Upgrade to a release after 4.3
Interim mitigation

Implement proper authentication and authorization checks on siteadmin/useredit.php to ensure only authenticated administrators can access user modification functions.

Fix this in Video Share Enterprise Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-2017 — 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-2007-2017 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