LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6565: InfiniteWP Client <= 1.12.3 - Unauthenticated Sensitive Information Exposure

The InfiniteWP Client plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.12.3 via the multi-call backup option. This makes it possible for unauthenticated attackers to extract sensitive data from a temporary SQL file via repeated GET requests during the limited time window of the backup process.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-6565 affects the InfiniteWP Client WordPress plugin through version 1.12.3. During a backup, an unauthenticated attacker may be able to retrieve sensitive database content from a temporary SQL file. The attack window is limited and rated high complexity, but exposed database data could still be business-sensitive.

Executive priority

Treat this as a moderate priority for WordPress environments using InfiniteWP Client. It is not confirmed actively exploited in the provided sources, but the potential exposure is sensitive database content, so remediation should be scheduled promptly.

Technical view

The flaw is sensitive information exposure via the plugin's multi-call backup option. Repeated unauthenticated GET requests during the backup process can expose a temporary SQL file. CVSS is 5.9 with network access, no privileges, no user interaction, high attack complexity, and high confidentiality impact.

Likely exposure

Public WordPress sites running InfiniteWP Client version 1.12.3 or earlier are the relevant exposure. Risk is highest where backups run while the site is internet-accessible and temporary backup artifacts can be reached by unauthenticated users.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation appears timing-dependent because it requires the limited backup window, which matches the high attack complexity rating.

Researcher notes

The key uncertainty is operational exploitability in a given environment because access depends on backup timing and temporary file exposure. Focus validation on version state, backup windows, artifact accessibility, and logs around backup activity.

Mitigation direction

  • Upgrade InfiniteWP Client to a release newer than 1.12.3 where available.
  • Check InfiniteWP and WordPress plugin guidance for the definitive fixed release.
  • Temporarily disable or remove the plugin if it cannot be updated promptly.
  • Restrict public access during backup operations where operationally feasible.
  • Review backup handling for leftover web-accessible SQL temporary files.

Validation and detection

  • Inventory WordPress sites for InfiniteWP Client and record installed versions.
  • Confirm no production site is running InfiniteWP Client 1.12.3 or earlier.
  • Review web logs for suspicious repeated unauthenticated requests during backup windows.
  • Verify backup temporary SQL files are not publicly accessible after backup completion.
  • Retest after updating to confirm the vulnerable version is no longer present.
Prepared
Confidence
high
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.

cwe · low confidence lookup

CWE-922: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-6565 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
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/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
3Source 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
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2023-6565Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
revmakxInfiniteWP Client0unaffected
Weakness

CWE details

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

CWE-922 · source CWE mapping

Insecure Storage of Sensitive Information

Insecure Storage of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.