LiveActive security incident?Get immediate response
CVE Record

CVE-2023-51490: WordPress Defender Security Plugin <= 4.1.0 is vulnerable to Sensitive Data Exposure

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in WPMU DEV Defender Security – Malware Scanner, Login Security & Firewall.This issue affects Defender Security – Malware Scanner, Login Security & Firewall: from n/a through 4.1.0.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-51490 is a sensitive information exposure issue in the WordPress Defender Security plugin through version 4.1.0. An unauthenticated remote actor may be able to access information exposed through log handling. Impact appears limited to confidentiality, but exposed logs can still reveal operational or security-sensitive details.

Executive priority

Treat this as a moderate-priority hygiene and exposure-reduction issue. It is not documented as actively exploited, but unauthenticated log exposure can leak information that helps later attacks.

Technical view

The record describes CWE-532, insertion or exposure of sensitive information in log files, affecting WPMU DEV Defender Security through 4.1.0. CVSS 3.1 is 5.3 with network access, low complexity, no privileges, no user interaction, unchanged scope, and low confidentiality impact only.

Likely exposure

Exposure is most likely on WordPress sites running Defender Security – Malware Scanner, Login Security & Firewall version 4.1.0 or earlier, especially where plugin log files are web-accessible or contain sensitive operational data.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates the issue is remotely reachable without authentication or user interaction, but only low confidentiality impact is documented.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, CWE-532, affected range through 4.1.0, and Patchstack vulnerability reference. No exploit details, confirmed exploitation, or named fixed version were provided in the bundle.

Mitigation direction

  • Inventory WordPress sites using the Defender Security plugin.
  • Upgrade affected installations beyond version 4.1.0 after checking vendor guidance.
  • Restrict public access to plugin log files and log directories.
  • Review exposed logs for credentials, tokens, or security-sensitive details.
  • Rotate any secrets found in potentially exposed logs.

Validation and detection

  • Confirm installed Defender Security versions across WordPress assets.
  • Check whether plugin log paths are publicly reachable.
  • Review server access logs for requests to Defender Security log files.
  • Verify logs no longer contain sensitive data after remediation.
  • Document affected sites, remediation dates, and residual exposure.
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 · low confidence lookup

CWE-532: 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-51490 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-51490Attack 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
WPMU DEVDefender Security – Malware Scanner, Login Security & Firewalldefender-security, n/aunaffected
Weakness

CWE details

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

CWE-532 · source CWE mapping

Insertion of Sensitive Information into Log File

Insertion of Sensitive Information into Log File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.