LiveActive security incident?Get immediate response
CVE Record

CVE-2021-27312: Server Side Request Forgery (SSRF) vulnerability in Gleez Cms 1.2.0, allows remote attackers to execute arb...

Server Side Request Forgery (SSRF) vulnerability in Gleez Cms 1.2.0, allows remote attackers to execute arbitrary code and obtain sensitive information via modules/gleez/classes/request.php.

CriticalCVSS 9.4Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-27312 is a critical SSRF issue reported in Gleez CMS 1.2.0. A remote unauthenticated attacker may be able to make the server issue unintended requests, with reported impacts including sensitive data exposure and arbitrary code execution.

Executive priority

Treat this as urgent for any live Gleez CMS 1.2.0 site, especially internet-facing systems. The score and reported impact justify rapid inventory, containment, and vendor-guidance review, even without confirmed active exploitation.

Technical view

The CVE describes CWE-918 in modules/gleez/classes/request.php for Gleez CMS 1.2.0. CVSS 3.1 is 9.4: network reachable, low complexity, no privileges, no user interaction, with high confidentiality and integrity impact and low availability impact.

Likely exposure

Exposure is most likely on internet-facing Gleez CMS 1.2.0 deployments. The provided affected-product metadata is incomplete, so teams should validate by installed application and version rather than relying on CPE matching.

Exploitation context

CISA KEV status is false in the bundle, and the provided sources do not establish active exploitation. Public GitHub and gist references exist, so defenders should assume technical details may be discoverable without treating exploitation as confirmed.

Researcher notes

Evidence is limited but specific: SSRF, file path, version, CWE-918, and CVSS vector are provided. The bundle does not include a confirmed patch, reliable CPE data, or KEV listing, so conclusions should stay tied to Gleez CMS 1.2.0 only.

Mitigation direction

  • Identify any Gleez CMS 1.2.0 instances and prioritize them for review.
  • Check the Gleez project issue and vendor guidance for a supported fix.
  • Restrict server outbound access to internal networks and metadata services.
  • Isolate, disable, or decommission affected instances if no supported fix exists.

Validation and detection

  • Confirm whether Gleez CMS 1.2.0 is deployed in production or externally reachable.
  • Review modules/gleez/classes/request.php presence and application version evidence.
  • Check web and egress logs for unexpected server-initiated requests.
  • Verify network controls block CMS access to sensitive internal endpoints.
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.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material 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-2021-27312 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
Critical
CVSS
9.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

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.

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

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.4CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L3.95.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.4Critical
CVSS 3.1 vector shape for CVE-2021-27312Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.