dbcve.org
Ms TopsitesApplication

CVE-2007-5918

MEDIUM · 6.0 CVSS v2.0 Published 2007-11-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
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
Cross-site request forgery (CSRF) vulnerability in edit.php in the MS TopSites add-on for PHP-Nuke does not verify that the uname parameter matches the current account, which allows remote authenticated users to change arbitrary accounts or change the SiteTitleName field as an arbitrary user via a modified uname value in an edit action to modules.php.

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

CSRF vulnerability in edit.php of the MS TopSites add-on for PHP-Nuke allows authenticated users to modify arbitrary user accounts by providing a modified 'uname' parameter. The application fails to verify that the requested username matches the currently authenticated user, enabling privilege escalation where one user can change another user's account settings or SiteTitleName field.

MitigationImplement proper session validation to verify the uname parameter matches the currently authenticated user's session before processing edit actions. Consider adding anti-CSRF tokens for all state-changing operations.

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
Ms TopsitesApplication
Affected:all versions

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
M
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:S/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. Identify if MS TopSites module is installed
    Locate the topsites module directory in your PHP-Nuke installation (typically in modules/ or similar path). Look for directory names containing 'topsites' or 'ms topsites'. Check your PHP-Nuke modules administration panel for installed modules.
    Affected if MS TopSites module is found in the PHP-Nuke modules directory or listed as installed in the admin panel
  2. Locate the edit.php file
    Navigate to the MS TopSites module directory and locate edit.php. Common path: modules/MS_Topsites/edit.php or modules/TopSites/edit.php.
    Affected if edit.php file exists in the MS TopOpsites module directory
  3. Inspect edit.php for uname parameter handling
    Open edit.php and search for the 'uname' parameter handling (look for $_POST['uname'] or $_GET['uname']). Check if the code verifies that the submitted 'uname' value matches the currently authenticated user's username from the session.
    Affected if The code uses $_POST['uname'] or $_GET['uname'] without comparing it to the authenticated user's session username (e.g., $user->data['username'] or $_SESSION['user']) before processing the edit action
  4. Check for session validation before edit operations
    In edit.php, locate the section that processes the edit action. Verify if there is a validation check that confirms the authenticated session user matches the 'uname' parameter being processed. Look for conditional statements like 'if ($uname == $user->data[username])' or equivalent session validation.
    Affected if No session validation exists to confirm the 'uname' parameter matches the currently authenticated user before allowing account modifications
  5. Verify the application processes edit requests
    As an authenticated user, attempt to access edit.php and observe if the application accepts a modified 'uname' parameter to modify another user's account. Check if arbitrary user account modifications are possible.
    Affected if The application allows modifying user accounts other than the currently authenticated user by supplying a different 'uname' parameter value

If MS TopSites is installed and edit.php processes the 'uname' parameter without validating it against the authenticated user's session, the environment is vulnerable to CVE-2007-5918.

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 proper session validation to verify the uname parameter matches the currently authenticated user's session before processing edit actions. Consider adding anti-CSRF tokens for all state-changing operations.

Fix this in Ms Topsites Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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