LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39503: PHPMyWind 5.6 is vulnerable to Remote Code Execution.

PHPMyWind 5.6 is vulnerable to Remote Code Execution. Becase input is filtered without "<, >, ?, =, `,...." In WriteConfig() function, an attacker can inject php code to /include/config.cache.php file.

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

Security readout for executives and security teams

Plain-English summary

CVE-2021-39503 describes remote code execution in PHPMyWind 5.6. The reported flaw allows attacker-controlled PHP code to be written into a cached configuration file. If a vulnerable site exposes the affected configuration-writing path, compromise could lead to server-side code execution.

Executive priority

Treat this as a priority for any internet-facing PHPMyWind 5.6 deployment because the reported impact is remote code execution. Urgency is lower for environments where the product is absent or configuration paths are not reachable.

Technical view

The source bundle states that PHPMyWind 5.6 filters input incompletely in WriteConfig(), allowing PHP code injection into /include/config.cache.php. No CVSS, CWE, CPE, authentication requirement, patch version, or vendor mitigation is provided in the bundled record.

Likely exposure

Exposure appears limited to deployments of PHPMyWind 5.6. The bundle does not identify CPEs, later affected versions, hosted services, or whether exploitation requires authentication or administrator access.

Exploitation context

The CVE is not marked as CISA KEV in the bundle. Public GitHub references are listed, but the provided evidence does not establish active exploitation, exploit maturity, or exploitation at scale.

Researcher notes

The core evidence is sparse. The record names WriteConfig() and /include/config.cache.php, but lacks CVSS, CWE, CPE, authentication context, affected range, and remediation details. Validate against the referenced GitHub material before making broad exposure claims.

Mitigation direction

  • Check PHPMyWind vendor or project guidance for a fixed version or official mitigation.
  • Upgrade or replace PHPMyWind 5.6 if a safe maintained release is available.
  • Restrict public access to administrative or configuration-writing functionality.
  • Review /include/config.cache.php for unauthorized PHP content.
  • Preserve logs and rebuild from clean sources if tampering is found.

Validation and detection

  • Inventory internet-facing sites for PHPMyWind 5.6 usage.
  • Confirm whether /include/config.cache.php exists and is writable by the application.
  • Review web and application logs for unexpected configuration update activity.
  • Inspect the cached configuration file for unexpected PHP code.
  • Verify whether the project has published a patch or advisory.
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

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
cve · low confidence lookup

CVE-2021-39503 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.