LiveActive security incident?Get immediate response
CVE Record

CVE-2017-5959: CSRF token bypass in GeniXCMS before 1.0.2 could result in escalation of privileges.

CSRF token bypass in GeniXCMS before 1.0.2 could result in escalation of privileges. The forgotpassword.php page can be used to acquire a token.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

GeniXCMS versions before 1.0.2 had a CSRF token bypass that could allow privilege escalation. The public description says the forgotpassword.php page could be used to obtain a token. Organizations not running GeniXCMS, or already on 1.0.2 or later, are not indicated as exposed by the provided sources.

Executive priority

Prioritize remediation if GeniXCMS is internet-facing or used for administrative content workflows. The likely business risk is unauthorized privilege elevation, but urgency is tempered by limited source evidence and no cited active exploitation.

Technical view

CVE-2017-5959 describes a CSRF protection bypass in GeniXCMS before 1.0.2. The reported issue involves acquiring a CSRF token through forgotpassword.php, weakening token-based request protection and potentially enabling privilege escalation. The source bundle does not provide CVSS, CWE, CPE, exploit maturity, or detailed affected configuration data.

Likely exposure

Exposure appears limited to deployments of GeniXCMS before version 1.0.2. The provided CVE data lists no CPEs and does not identify hosted services, distributions, plugins, or downstream packages. Confirm exposure through direct software inventory rather than product-name matching alone.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Public references include the GitHub issue and the v1.0.2 release. Treat this as a known public vulnerability, but do not assume exploitation without additional evidence.

Researcher notes

Evidence is sparse: the CVE description identifies the vulnerability class, affected version boundary, and token acquisition path, but omits scoring, prerequisites, and detailed impact. Researchers should anchor analysis to the GitHub issue and release, avoiding assumptions about exploitability beyond privilege-escalation potential.

Mitigation direction

  • Upgrade GeniXCMS to version 1.0.2 or later.
  • Review the v1.0.2 release notes and linked issue for vendor context.
  • Limit administrative access to trusted users and networks where possible.
  • Review password reset and privilege-change activity for anomalies.
  • Check vendor guidance if maintaining a fork or modified deployment.

Validation and detection

  • Inventory all GeniXCMS deployments and record exact versions.
  • Confirm no production instance remains below version 1.0.2.
  • Review whether forgotpassword.php is present and externally reachable.
  • Validate CSRF protection behavior in a controlled, authorized test environment.
  • Check account privilege changes around the remediation window.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-5959 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.