Security readout for executives and security teams
Plain-English summary
ClanSphere 2011.3 has a file-reading flaw that can let an unauthenticated remote attacker read files the web server can access. The issue is in how the application handles the cs_lang cookie. This is serious for any exposed legacy ClanSphere site because file disclosure can reveal credentials, configuration, or other sensitive server data.
Executive priority
Prioritize remediation for any public ClanSphere 2011.3 instance. The vulnerability enables sensitive file disclosure without authentication, and public exploit references increase operational risk even without confirmed active exploitation.
Technical view
CVE-2012-10034 is a CWE-22 local file inclusion issue in ClanSphere 2011.3. Unsanitized cs_lang cookie input allows directory traversal, and the source bundle notes null byte injection can bypass extension checks. CVSS 4.0 is 8.7. Public exploit references exist, but the provided sources do not show CISA KEV listing or active exploitation.
Likely exposure
Exposure is likely limited to organizations still running ClanSphere 2011.3, especially internet-facing community or clan sites. The source bundle does not identify other affected versions or CPEs.
Exploitation context
Public exploit artifacts are cited by Rapid7 Metasploit and Exploit-DB references. However, KEV is false, and the supplied evidence does not establish active exploitation in the wild.
Researcher notes
The record is source-grounded but sparse. Evidence supports ClanSphere 2011.3, CWE-22, unauthenticated network exposure, high confidentiality impact, and public exploit availability. No official patch, broader version range, or active exploitation evidence is present in the supplied bundle.
Mitigation direction
- Inventory and identify any ClanSphere 2011.3 deployments.
- Check ClanSphere project or vendor guidance for fixed versions or official workarounds.
- Remove public exposure until the application is upgraded, replaced, or isolated.
- Review configuration files and credentials for possible disclosure risk.
- Rotate secrets if logs suggest suspicious file access attempts.
Validation and detection
- Confirm the running ClanSphere version from application files or admin metadata.
- Review web logs for suspicious cs_lang cookie values.
- Check whether the site is reachable from the internet.
- Assess whether sensitive files are readable by the web server account.
- Document compensating controls if upgrade or replacement is delayed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2012-10034 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/auxiliary/scanner/http/clansphere_traversal.rbCVE reference · exploit
- https://www.exploit-db.com/exploits/22181CVE reference · exploit
- https://sourceforge.net/projects/clansphere/CVE reference · product
- https://www.vulncheck.com/advisories/clansphere-local-file-inclusion-via-cookieCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.