CVE-2006-5722
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 · uneditedMultiple PHP remote file inclusion vulnerabilities in Segue CMS 1.5.9 and earlier, when magic_quotes_gpc is enabled, allow remote attackers to execute arbitrary PHP code via a URL in the theme parameter to (1) themesettings.php or (2) index.php, a different vector than CVE-2006-5497. NOTE: the provenance of this information is unknown; the details are obtained solely 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 confidenceSegue CMS 1.5.9 and earlier contains remote file inclusion vulnerabilities in themesettings.php and index.php. The theme parameter accepts a URL, allowing remote attackers to inject and execute arbitrary PHP code when magic_quotes_gpc is enabled.
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.5.9= 1.3.5= 1.5.7= 1.5.8CVSS 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.
-
Confirm Segue CMS installationSearch web server directories for Segue CMS files, typically in /segue, /cms, or the web root. Look for characteristic files like themesettings.php, index.php, or config files.Affected if Segue CMS files are found on the server in a web-accessible directory.
-
Identify Segue CMS versionOpen the main index.php or admin/config file in a text editor or via web browser. Check for version strings like '1.5.9', '1.5.8', '1.5.7', '1.3.5' in the source code or page footer.Affected if The installed version is 1.5.9, 1.5.8, 1.5.7, or 1.3.5 (or any version <= 1.5.9).
-
Locate vulnerable PHP filesVerify the presence of themesettings.php and index.php in the Segue CMS installation directory. These files should exist in the web-accessible portion of the application.Affected if Both themesettings.php and index.php exist in the Segue CMS web directory.
-
Check theme parameter exposureExamine the source code of themesettings.php and index.php. Look for code that reads a 'theme' parameter (e.g., $_GET['theme']) and passes it to include() or require() without sanitization.Affected if The theme parameter is processed and used in include/require statements without validation.
-
Verify PHP allows remote includesCheck PHP configuration (php.ini) for the settings allow_url_fopen=On and allow_url_include=On. These can be checked via phpinfo() or by reviewing the PHP configuration file.Affected if allow_url_fopen or allow_url_include is enabled in PHP configuration.
A user is affected if Segue CMS version 1.5.9 or earlier is installed, the vulnerable themesettings.php or index.php files exist, and PHP has allow_url_fopen or allow_url_include enabled, allowing the theme parameter to include remote URLs.
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 strict input validation on the theme parameter to reject URLs/paths from untrusted sources, or whitelist allowed theme values. Consider disabling allow_url_fopen and allow_url_include in PHP configuration.
- 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-2006-5722 — 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-2006-5722 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