CVE-2005-2691
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 · uneditedincludes/common.php in RunCMS 1.2 and earlier calls the extract function with EXTR_OVERWRITE on HTTP POST variables, which allows remote attackers to overwrite arbitrary variables, possibly allowing execution of arbitrary code.
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 confidenceRunCMS 1.2 and earlier includes/common.php uses the PHP extract() function with EXTR_OVERWRITE flag on HTTP POST variables, allowing remote attackers to overwrite arbitrary PHP variables in the application scope by supplying variable names as POST parameters, potentially leading to arbitrary code execution.
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.1= 1.1a= 1.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if RunCMS is installedLook for RunCMS in your web root directory. Check for typical RunCMS folders such as /runcms, /cms, or the main index.php file with RunCMS branding.Affected if RunCMS is present on the server
-
Determine the RunCMS versionCheck the version file or the main index.php for the version string. Common locations include version.php, or the admin panel about section.Affected if The installed version is 1.1, 1.1a, or 1.2
-
Locate the vulnerable fileNavigate to includes/common.php within the RunCMS installation directory. Verify the file exists.Affected if The file includes/common.php exists in the RunCMS installation
-
Check for the vulnerable extract() patternOpen includes/common.php and search for extract($_POST with EXTR_OVERWRITE or extract($_REQUEST with EXTR_OVERWRITE. This pattern allows POST parameters to overwrite application variables.Affected if The file contains extract() called with EXTR_OVERWRITE on POST or REQUEST superglobals
-
Verify PHP is processing the applicationConfirm that PHP is enabled and the RunCMS site is accessible via a web server. The vulnerability only triggers when PHP processes the affected code.Affected if PHP is processing the RunCMS application
You are affected if RunCMS version 1.1, 1.1a, or 1.2 is installed and includes/common.php contains extract() with EXTR_OVERWRITE on POST variables.
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 dataReplace extract() with EXTR_OVERWRITE on POST variables with safer alternatives such as EXTR_SKIP or EXTR_IF_EXISTS, or manually define expected variables; also upgrade to a patched version if available.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2691 — 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-2005-2691 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