LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6064: PayHere Payment Gateway < 2.2.12 - Unauthenticated Log Data Disclosure

The PayHere Payment Gateway WordPress plugin before 2.2.12 automatically creates publicly-accessible log files containing sensitive information when transactions occur.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Affected WordPress sites may have exposed payment-related logs to anyone on the internet. The issue affects PayHere Payment Gateway versions before 2.2.12 and can disclose sensitive transaction information without login or user interaction.

Executive priority

Prioritize remediation for any payment-processing WordPress site. The main risk is confidentiality loss, not system takeover, but exposed transaction data can create regulatory, fraud, and customer-trust impact.

Technical view

CVE-2023-6064 is a CWE-200 information disclosure flaw. The plugin automatically creates publicly accessible log files when transactions occur. CVSS 3.1 is 7.5, reflecting network access, low complexity, no privileges, no user interaction, and high confidentiality impact only.

Likely exposure

Exposure is most likely on WordPress sites running PayHere Payment Gateway before 2.2.12, especially sites that processed transactions while vulnerable logging was enabled or present.

Exploitation context

The bundled WPScan reference is tagged as exploit-related, but the source bundle does not establish active exploitation. CISA KEV status is false, so treat exploitation as plausible but not confirmed from these sources.

Researcher notes

The bundle does not provide exact log paths, exposed fields, or confirmed exploitation. Use vendor and WPScan details to refine detection, but avoid assuming additional affected products or behavior beyond versions before 2.2.12.

Mitigation direction

  • Upgrade PayHere Payment Gateway to version 2.2.12 or later.
  • Check vendor guidance for any additional cleanup or hardening steps.
  • Remove or secure any publicly reachable transaction log files.
  • Review whether exposed logs contained payment, customer, or transaction data.
  • Rotate affected secrets or credentials if logs contained them.

Validation and detection

  • Inventory WordPress sites using the PayHere Payment Gateway plugin.
  • Confirm installed plugin versions are 2.2.12 or later.
  • Check web-accessible plugin storage for exposed log files without collecting sensitive data.
  • Review web access logs for requests to known PayHere log locations.
  • Confirm sensitive transaction logs are not indexed, cached, or backed up publicly.
Prepared
Confidence
high
Sources
3

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

CVE-2023-6064 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

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
2Source 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-6064Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UnknownPayHere Payment Gateway0unaffected
Weakness

CWE details

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.