dbcve.org
TopoApplication · Ej3

CVE-2006-3536

HIGH · 7.5 CVSS v2.0 Published 2006-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Direct static code injection vulnerability in code/class_db_text.php in EJ3 TOPo 2.2.178 and earlier allows remote attackers to execute arbitrary PHP code via parameters such as (1) descripcion and (2) pais, which are stored directly in a PHP script. NOTE: the provenance of this information is unknown; the details are obtained solely from third party reports.

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 confidence

Direct static code injection vulnerability in EJ3 TOPo 2.2.178 and earlier allows remote attackers to execute arbitrary PHP code via 'descripcion' and 'pais' parameters that are stored directly into PHP script files without sanitization, enabling full remote code execution.

MitigationImplement strict input validation and sanitization before storing user input into PHP files; remove direct storage of unsanitized user input into code files, or upgrade to a patched version if available.

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
TopoApplication
Affected:= 2.2= 2.2.178

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify EJ3 TOPo installation and version
    Search the web server for EJ3 TOPo files (common paths: /ej3topo/, /topo/, or check for files containing 'EJ3 TOPo' or 'topo' in title). Look for version information in README, index, or config files. Compare the found version to 2.2 and 2.2.178 (and earlier).
    Affected if EJ3 TOPo version 2.2, 2.2.178, or any version earlier than 2.2.178 is installed.
  2. Locate forms accepting descripcion and pais parameters
    Search web application source code (PHP files) for occurrences of the parameters 'descripcion' and 'pais'. Check if these parameters are accepted via GET or POST requests in any PHP script.
    Affected if The application contains PHP code that accepts 'descripcion' or 'pais' parameters from user input.
  3. Check for file write operations storing user input
    Examine PHP scripts that handle 'descripcion' and 'pais' parameters. Look for file write operations (fwrite, file_put_contents, or similar) that store these parameter values. Identify the target file being written to.
    Affected if User input from 'descripcion' or 'pais' parameters is being written to files on the server.
  4. Verify if written files have .php extension
    Inspect the file write operations identified in the previous step. Determine the extension of the file where user input is being stored. Look for .php extensions in the write target path.
    Affected if User input is being stored directly into files with a .php extension.
  5. Confirm lack of input sanitization before storage
    Review the PHP code handling 'descripcion' and 'pais' parameters. Check if there is any sanitization, escaping, or validation performed before the input is written to the file. Look for functions like htmlspecialchars, addslashes, or validation logic.
    Affected if User input from 'descripcion' or 'pais' is written to PHP files without any sanitization or validation (the input is stored raw).

The environment is affected if EJ3 TOPo version 2.2 or earlier is installed AND the application writes unsanitized user input from 'descripcion' or 'pais' parameters directly into PHP files accessible via web.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization before storing user input into PHP files; remove direct storage of unsanitized user input into code files, or upgrade to a patched version if available.

Fix this in Topo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-3536 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-3536 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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