dbcve.org
BasercmsApplication

CVE-2012-1248

MEDIUM · 5.1 CVSS v2.0 Published 2012-05-15
Fix available
A fix is available. Upgrade to after 1.6.15 or later.
See remediation →
60/100
Remediation priority · Elevated
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
app/config/core.php in baserCMS 1.6.15 and earlier does not properly handle installations in shared-hosting environments, which allows remote attackers to hijack sessions by leveraging administrative access to a different domain.

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

In baserCMS 1.6.15 and earlier, the app/config/core.php file contains session configuration that does not properly isolate sessions in shared-hosting environments. When multiple domains share the same server, an attacker with administrative access to one domain can potentially hijack sessions from other domains hosted on the same server due to improper session cookie path or save_path settings.

MitigationIsolate session storage by configuring a unique session.save_path directory for each hosted site, set restrictive session.cookie_path and session.cookie_domain parameters in core.php, and consider implementing session regeneration on authentication to prevent session fixation attacks.

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
BasercmsApplication
Affected:<= 1.6.15= 1.5.4= 1.5.5= 1.5.6= 1.5.7= 1.5.8= 1.5.9= 1.6.0= 1.6.1= 1.6.2= 1.6.3= 1.6.4

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
High
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:H/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. Determine baserCMS version
    Locate the version file in your baserCMS installation - typically in a config file or version.php within the app directory
    Affected if The installed version is 1.6.15 or earlier, or matches any of these: 1.5.4, 1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.5.9, 1.6.0, 1.6.1, 1.6.2, 1.6.3, 1.6.4
  2. Locate the core.php configuration file
    Verify the presence of app/config/core.php in your baserCMS installation directory
    Affected if The file app/config/core.php exists and contains session configuration settings
  3. Inspect session.save_path setting
    Open app/config/core.php and search for the session.save_path parameter - check if it points to a shared or world-writable directory
    Affected if session.save_path is set to a common directory shared across multiple hosted sites, or is not set to a unique per-site path
  4. Inspect session.cookie_path and session.cookie_domain settings
    In app/config/core.php, locate session.cookie_path and session.cookie_domain parameters - verify if they restrict cookies to the specific domain
    Affected if session.cookie_path is set to a generic path like '/' or session.cookie_domain is not set/restricted to the specific domain, allowing cross-domain session access
  5. Verify shared hosting environment
    Confirm that multiple domains or sites are hosted on the same server and share the same session storage location
    Affected if Multiple domains share the same server with overlapping or shared session.save_path configurations

You are affected if running baserCMS version 1.6.15 or earlier with session configuration in app/config/core.php that does not isolate sessions per domain in a shared-hosting environment.

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
Upgrade available Upgrade to a release after 1.6.15
Interim mitigation

Isolate session storage by configuring a unique session.save_path directory for each hosted site, set restrictive session.cookie_path and session.cookie_domain parameters in core.php, and consider implementing session regeneration on authentication to prevent session fixation attacks.

Fix this in Basercms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-1248 — 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-2012-1248 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