LiveActive security incident?Get immediate response
CVE Record

CVE-2020-24140: Server-side request forgery in Wcms 0.3.2 let an attacker send crafted requests from the back-end server of...

Server-side request forgery in Wcms 0.3.2 let an attacker send crafted requests from the back-end server of a vulnerable web application via the pagename parameter to wex/html.php. It can help identify open ports, local network hosts and execute command on local services.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-24140 is a server-side request forgery issue reported in Wcms 0.3.2. A vulnerable site could be abused to make requests from its back-end server, potentially exposing internal hosts, open ports, or unsafe local services. The supplied sources do not provide CVSS scoring or confirm active exploitation.

Executive priority

Prioritize investigation if Wcms is internet-facing or runs near sensitive internal services. There is no active-exploitation evidence in the provided sources, but SSRF can turn a public web server into an internal network access point.

Technical view

The issue is described as SSRF through the pagename parameter in wex/html.php in Wcms 0.3.2. The reported impact includes internal port and host discovery, and possible command execution against local services. The source bundle does not identify a CPE, CWE, fixed version, or vendor mitigation.

Likely exposure

Exposure appears limited to deployments running Wcms 0.3.2 with the affected wex/html.php route reachable, especially internet-facing instances. The CVE record’s affected-product metadata is incomplete, so asset confirmation must come from internal inventory and application inspection.

Exploitation context

Public references include a GitHub issue and researcher write-up. The source bundle marks KEV as false and does not provide evidence of active exploitation. Treat the vulnerability as publicly documented but not confirmed as exploited in the wild by the provided evidence.

Researcher notes

Key gaps are missing CVSS, CWE, CPE, fixed version, and vendor remediation detail. Analysis should stay tied to Wcms 0.3.2 and the pagename parameter in wex/html.php. Do not assume other Wcms versions are affected without additional evidence.

Mitigation direction

  • Inventory any Wcms installations and confirm whether version 0.3.2 is present.
  • Check the Wcms project guidance for a fixed release or recommended remediation.
  • Restrict public access to affected Wcms routes where business use does not require exposure.
  • Apply conservative outbound filtering from web servers to internal-only services.
  • Monitor web logs for unexpected requests involving wex/html.php and pagename.

Validation and detection

  • Confirm whether wex/html.php exists and is reachable on Wcms assets.
  • Verify the installed Wcms version against the reported affected version 0.3.2.
  • Review application logs for suspicious pagename values or internal target patterns.
  • Check server egress controls to internal networks and localhost services.
  • Document findings because official affected-product metadata is incomplete.
Prepared
Confidence
medium
Sources
4

Public sources used

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

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-2020-24140 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.