CVE-2010-3688
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 · uneditedDirectory traversal vulnerability in ADMIN/login.php in NetArtMEDIA WebSiteAdmin allows remote emote attackers to include and execute arbitrary local files via directory traversal sequences in the lng parameter.
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 confidenceLocal file inclusion vulnerability in NetArtMEDIA WebSiteAdmin's ADMIN/login.php allows remote attackers to execute arbitrary local files via directory traversal sequences in the 'lng' parameter. The application fails to properly sanitize user input, enabling attackers to manipulate the parameter to traverse directories and include malicious files from the local filesystem.
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 dataall versionsCVSS 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 the vulnerable login.php fileSearch for the file ADMIN/login.php in the web root directory. Common paths include /ADMIN/login.php, /webadmin/ADMIN/login.php, or similar subdirectories under the web root.Affected if The file ADMIN/login.php exists in the web application directory structure.
-
Inspect the login.php source code for the 'lng' parameterOpen ADMIN/login.php and search for occurrences of the variable 'lng' (or $_GET['lng'], $_POST['lng']). Look for how this parameter is used in include(), require(), or similar functions.Affected if The code processes the 'lng' parameter and uses it in file inclusion functions without proper validation.
-
Verify lack of input sanitization on the 'lng' parameterExamine the code around the 'lng' parameter usage. Check if basename(), whitelist validation, or other input filtering is applied before the file inclusion.Affected if The 'lng' parameter is used directly in include/require statements without sanitization functions like basename() or whitelist checking.
-
Test for directory traversal vulnerability (if authorized)If you have authorization to test, send a request to ADMIN/login.php?lng=../../../../etc/passwd or similar traversal sequence and observe if file contents are returned.Affected if The application returns contents of files outside the intended language directory when traversal sequences are used in the 'lng' parameter.
You are affected if the NetArtMEDIA WebSiteAdmin application is installed and the ADMIN/login.php file processes the 'lng' parameter without proper sanitization, allowing directory traversal in file inclusions.
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 'lng' parameter to whitelist allowed language files or use basename() to strip directory traversal sequences. Alternatively, refactor to use a fixed mapping of language identifiers rather than direct file inclusion.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3688 — 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-2010-3688 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