CVE-2005-3796
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 admin_options_manage.php in AlstraSoft Affiliate Network Pro 7.2 allows attackers to execute arbitrary PHP code via the number parameter. NOTE: it is not clear from the original report whether administrator privileges are required. If not, then this does not cross privilege boundaries and is not a vulnerability.
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 confidenceA direct static code injection vulnerability exists in admin_options_manage.php in AlstraSoft Affiliate Network Pro 7.2. The 'number' parameter is not properly validated or sanitized before being used in PHP code execution, allowing attackers to inject and execute arbitrary PHP code.
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= 7.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.
-
Locate AlstraSoft Affiliate Network Pro installationSearch the web server document root for directories containing Alstrasoft or Affiliate Network Pro files. Check for characteristic files such as index.php, admin.php, or configuration files with version information.Affected if The product is not found on the system
-
Confirm installed version is 7.2Examine version.php, version.txt, README files, or configuration files within the installation directory for version number. Alternatively, access the admin dashboard and look for version information in the footer or about section.Affected if The installed version is not exactly 7.2
-
Verify vulnerable file admin_options_manage.php existsLocate admin_options_manage.php within the /admin/ subdirectory of the installation. The file should exist and contain PHP code.Affected if The file does not exist in the expected admin directory
-
Inspect code for unsafe 'number' parameter usageOpen admin_options_manage.php and examine how the 'number' parameter from $_GET or $_POST is handled. Look for patterns where this parameter is concatenated into eval(), preg_replace with /e modifier, or similar PHP code execution functions without validation.Affected if The code shows the 'number' parameter being directly used in eval() or similar dynamic code execution without input sanitization
The environment is affected only if AlstraSoft Affiliate Network Pro version 7.2 is confirmed installed AND the admin_options_manage.php file contains the vulnerable code pattern where the 'number' parameter is processed through unsafe code execution functions.
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 and sanitization on all parameters, particularly the 'number' parameter. Use whitelist validation for expected values, apply htmlspecialchars() for output encoding, and ensure proper authentication and authorization checks are enforced before allowing access to admin functionality.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-3796 — 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-3796 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