CVE-2007-5032
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 · uneditedCross-site request forgery (CSRF) vulnerability in admin.php in Francisco Burzi PHP-Nuke allows remote attackers to add administrative accounts via an AddAuthor action with modified add_name and add_radminsuper parameters.
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 confidenceCSRF vulnerability in PHP-Nuke's admin.php allows remote attackers to forge administrative account creation requests by tricking authenticated admins into visiting malicious pages, with attackers controlling the add_name and add_radminsuper parameters to create new superuser accounts.
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<= 1.0<= 2.5<= 3.0<= 4.0<= 4.0.4<= 4.3<= 4.4<= 4.4.1a<= 5.0<= 5.0.1<= 5.1<= 5.2CVSS 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify PHP-Nuke installation and versionLocate the PHP-Nuke installation and check the version number in the source code, typically found in version.php, mainfile.php, or the admin panel's 'System Info' pageAffected if The installed version matches or is less than any of the following: 1.0, 2.5, 3.0, 4.0, 4.0.4, 4.3, 4.4, 4.4.1a, 5.0, 5.0.1, 5.1, or 5.2
-
Verify admin.php exists and is accessibleCheck if the file admin.php exists in the web root or admin directory and is accessible via HTTPAffected if The admin.php file is present and the web server can serve it
-
Check for anti-CSRF protection in admin formsExamine the admin.php source code, specifically the sections handling add_name and add_radminsuper parameters, for the presence of anti-CSRF token validation or Referer header checksAffected if The admin.php code lacks anti-CSRF tokens (synchronizer token pattern) and does not validate the Referer header on the server side for AddAuthor actions
-
Inspect admin user creation functionalityReview the admin.php file for the add_author or user creation logic to confirm it accepts add_name and add_radminsuper parameters without proper authentication verificationAffected if The admin.php allows creation of new superuser accounts through add_name and add_radminsuper parameters without requiring a unique, per-request security token
A system is affected if it runs any Francisco Burzi Php Nuke version 5.2 or earlier and its admin.php lacks anti-CSRF token validation and Referer header checks for administrative account creation actions.
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 dataImplement anti-CSRF tokens (synchronizer token pattern) on admin forms and validate the Referer header on server-side to prevent forged AddAuthor actions.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5032 — 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-2007-5032 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