LiveActive security incident?Get immediate response
CVE Record

CVE-2020-24139: Server-side request forgery in Wcms 0.3.2 lets an attacker send crafted requests from the back-end server o...

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Wcms 0.3.2 has a server-side request forgery issue in a public PHP endpoint. An attacker may be able to make the web server send requests into networks or services the attacker cannot directly reach. The source claims this can support internal port and host discovery and possible command execution against local services.

Executive priority

Prioritize review if Wcms 0.3.2 is externally reachable. The business risk is unauthorized use of the server as a network pivot, which can expose internal services or amplify existing local-service weaknesses. Urgency is reduced only where the product is absent, isolated, or inaccessible to untrusted users.

Technical view

The reported flaw is SSRF through the path parameter of wex/cssjs.php in Wcms 0.3.2. The CVE description says crafted requests can originate from the backend server, enabling internal reconnaissance and interaction with local services. No CVSS, CWE, affected CPEs, or vendor-fixed version are provided in the supplied record.

Likely exposure

Exposure is most likely where Wcms 0.3.2 is internet-facing or reachable by untrusted users and the wex/cssjs.php endpoint is accessible. The CVE record’s affected-product metadata is incomplete, so confirm by installed application name, version, and endpoint presence rather than CPE matching alone.

Exploitation context

The supplied sources do not show CISA KEV listing or confirmed active exploitation. Public references describe the vulnerable parameter and impact class. Treat exploit maturity as publicly described but not proven actively exploited from the provided evidence.

Researcher notes

The evidence base is thin: the CVE record lacks CVSS, CWE, CPEs, and fixed-version data. The core claim is consistent across the supplied CVE description and GitHub references, but remediation details require project-specific confirmation. Avoid assuming all Wcms versions are affected.

Mitigation direction

  • Check the Wcms project or vendor guidance for a fixed release or official mitigation.
  • Remove, replace, or isolate Wcms 0.3.2 if no supported fix is available.
  • Restrict public access to wex/cssjs.php where business use permits.
  • Limit web-server outbound access to internal hosts, localhost, and sensitive services.
  • Review logs for unusual path parameter values referencing remote or internal resources.

Validation and detection

  • Inventory web applications for Wcms and confirm any 0.3.2 deployments.
  • Verify whether wex/cssjs.php is reachable from untrusted networks.
  • Review access logs for suspicious requests to wex/cssjs.php.
  • Confirm outbound filtering prevents application-initiated access to internal services.
  • Use only approved, controlled SSRF validation in non-production or authorized test scopes.
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

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