CVE-2006-2129
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 · uneditedDirect static code injection vulnerability in Pro Publish 2.0 allows remote authenticated administrators to execute arbitrary PHP code by editing certain settings, which are stored in set_inc.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 confidenceA direct static code injection vulnerability in Pro Publish 2.0 allows remote authenticated administrators to inject arbitrary PHP code into the set_inc.php file through certain setting modifications. When the compromised file is subsequently included by the application, the injected code executes server-side.
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= 2.0CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:S/C:P/I:P/A:N
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 Pro Publish installationLocate the Pro Publish application on the web server. Check for the presence of index.php or admin.php files that identify the Deltascripts Pro Publish application.Affected if The application is present on the server.
-
Verify version is 2.0Inspect the application files for a version identifier. Common locations include a version.php file, the footer or header templates, or an about/admin panel page displaying the version number.Affected if The installed version is exactly 2.0.
-
Locate set_inc.php fileSearch the application directory for a file named set_inc.php, typically found in the includes or configuration folder. Use file system search or check common paths like ./includes/set_inc.php or ./config/set_inc.php.Affected if The set_inc.php file exists in the application directory.
-
Check if settings stored in PHP filesExamine set_inc.php or similar configuration files to determine if settings are stored as executable PHP code (look for PHP tags containing variable assignments). Also check if the application writes settings directly to PHP files rather than using a database or flat config format.Affected if Settings are stored in executable PHP files and the application writes to these files through admin functionality.
-
Assess admin panel exposureDetermine if the admin panel is accessible to untrusted users. Check for authentication requirements on admin.php or similar admin entry points, and whether the panel is exposed to the internet or restricted to local access.Affected if The admin panel is accessible to remote, untrusted users.
A user is affected if Deltascripts Pro Publish version 2.0 is installed with the set_inc.php file present and the admin panel accessible to untrusted remote users.
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 dataRestrict admin panel access to trusted IP addresses/networks, implement strict input validation on all setting parameters before writing to set_inc.php, and migrate settings storage from executable PHP files to a database or structured configuration format.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-2129 — 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-2129 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