LiveActive security incident?Get immediate response
CVE Record

CVE-2015-5243: phpWhois allows remote attackers to execute arbitrary code via a crafted whois record.

phpWhois allows remote attackers to execute arbitrary code via a crafted whois record.

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

Security readout for executives and security teams

Plain-English summary

CVE-2015-5243 describes a remote code execution flaw in phpWhois: a malicious whois record could cause code to run in an application using the library. The bundle does not include CVSS, CWE, or precise affected-version data, so urgency depends on whether phpWhois is deployed and reachable through whois lookups.

Executive priority

Prioritize inventory and patch verification for any internet-facing service using phpWhois. Remote code execution can become business-critical, but the lack of version and exploitation evidence means the first decision point is confirming actual deployment.

Technical view

The CVE record states phpWhois allows remote attackers to execute arbitrary code through a crafted whois record. References include an upstream issue, advisory, blog, changelog, and repository commits, indicating code changes exist. The bundle does not specify vulnerable or fixed versions.

Likely exposure

Exposure is most relevant for web applications, admin tools, or backend services that use phpWhois to retrieve and parse external whois records. The provided affected-product metadata is incomplete, so inventory confirmation is required.

Exploitation context

The provided sources support remote code execution through crafted whois data, but KEV is false and the bundle provides no evidence of active exploitation. Public references suggest the issue is documented, so defenders should treat reachable deployments seriously.

Researcher notes

The bundle names phpWhois and describes crafted whois records as the attack vector, but omits CVSS, CWE, CPEs, and affected ranges. Do not assume all forks or versions are affected without comparing the referenced commits and changelog.

Mitigation direction

  • Identify all applications and dependencies using phpWhois or phpwhois forks.
  • Review linked vendor commits, changelog, and advisory for fixed versions.
  • Upgrade or replace vulnerable phpWhois code according to vendor guidance.
  • Restrict whois lookup features from untrusted users where feasible.
  • Monitor logs for unusual whois lookup errors or parser failures.

Validation and detection

  • Search dependency manifests and vendored code for phpWhois references.
  • Confirm deployed library version against upstream changelog and commits.
  • Test whether public routes trigger server-side whois parsing.
  • Review code paths that parse external whois records.
  • Document compensating controls if upgrade timing is delayed.
Prepared
Confidence
medium
Sources
8

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-2015-5243 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
7Source 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.