LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47668: WordPress Restrict Content Plugin <= 3.2.7 is vulnerable to Sensitive Data Exposure

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in StellarWP Membership Plugin – Restrict Content plugin <= 3.2.7 versions.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-47668 is a medium-severity information exposure issue in the WordPress Restrict Content plugin from StellarWP, affecting versions up to 3.2.7. The cited record describes unauthorized access to sensitive information, with Patchstack identifying log-file exposure. It does not describe system takeover or data alteration.

Executive priority

Treat this as a near-term WordPress hygiene issue, not an emergency unless affected sites handle sensitive member data or expose logs publicly. Prioritize inventory, version verification, and access-control review.

Technical view

The issue is classified as CWE-200 with CVSS 3.1 score 5.3: network-accessible, low complexity, no privileges, no user interaction, low confidentiality impact only. The public bundle identifies the package as restrict-content and affected scope as Restrict Content plugin <= 3.2.7.

Likely exposure

Exposure is most likely on WordPress sites running StellarWP Restrict Content at version 3.2.7 or earlier, especially where plugin or server logs are accessible outside authorized administrative paths.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates remote unauthenticated exposure is possible, but the available sources do not provide exploit maturity, observed attacks, or a confirmed fixed version.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack reference. The bundle supports sensitive information exposure via log file, CVSS 5.3, and affected versions <= 3.2.7, but does not include exploit details, active exploitation, or explicit fixed-version text.

Mitigation direction

  • Inventory WordPress sites using the Restrict Content plugin.
  • Check StellarWP or Patchstack guidance for the supported fixed release.
  • Upgrade affected Restrict Content installations when a vendor-confirmed fix is available.
  • Restrict public access to application, plugin, and server log files.
  • Review logs for sensitive data and reduce unnecessary sensitive logging.

Validation and detection

  • Confirm the installed plugin slug is restrict-content.
  • Check whether the installed version is 3.2.7 or earlier.
  • Verify log files are not publicly reachable without authorization.
  • Review WordPress and hosting access controls for log directories.
  • Document remediation status for each affected site.
Prepared
Confidence
medium
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-47668 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
StellarWPMembership Plugin – Restrict Contentrestrict-content, n/aunaffected
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.