LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31550: WordPress WP-LESS plugin <= 1.9.6 - Sensitive Data Exposure vulnerability

Insertion of Sensitive Information into Externally-Accessible File or Directory vulnerability in thom4 WP-LESS wp-less allows Retrieve Embedded Sensitive Data.This issue affects WP-LESS: from n/a through <= 1.9.6.

MediumCVSS 5.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31550 is a medium-severity information exposure issue in the WordPress WP-LESS plugin. A vulnerable site may place sensitive information in files or directories that can be reached externally. The main business risk is unintended disclosure, not site takeover based on the provided sources.

Executive priority

Treat as a prompt but not emergency remediation item. Prioritize internet-facing WordPress properties and any site where WP-LESS may process configuration, credentials, or proprietary data into public files.

Technical view

The CVE maps to CWE-538: sensitive information inserted into an externally accessible file or directory. The provided CVSS 3.1 score is 5.8 with network access, low attack complexity, no privileges, no user interaction, changed scope, and low confidentiality impact only.

Likely exposure

Exposure appears limited to WordPress sites running thom4 WP-LESS through the affected range stated as <= 1.9.6. The bundle does not identify affected hosting providers, default WordPress core exposure, or non-WordPress products.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. The issue is remotely reachable by CVSS, but the sources do not provide exploit maturity, observed attacks, or public proof-of-concept status.

Researcher notes

Version evidence is somewhat inconsistent: the CVE description states through <= 1.9.6, while the Patchstack URL references 1.9.3.3. The affected object also contains sparse version data. Validate against vendor or Patchstack before closing exposure.

Mitigation direction

  • Inventory WordPress sites for the WP-LESS plugin and installed version.
  • Check vendor, WordPress plugin, and Patchstack guidance for fixed versions or official remediation.
  • Disable or remove WP-LESS where it is not business-critical.
  • Review exposed plugin-generated files for secrets or sensitive configuration data.
  • Rotate any credentials confirmed to have been exposed.

Validation and detection

  • Confirm whether WP-LESS is installed on each internet-facing WordPress site.
  • Compare installed versions against the CVE range and Patchstack advisory details.
  • Review public web-accessible plugin output for embedded sensitive values.
  • Check access logs for unusual requests to plugin-generated files.
  • Document whether any sensitive data was actually exposed.
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-538: 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-2025-31550 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.8 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

5.8Medium
CVSS 3.1 vector shape for CVE-2025-31550Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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
thom4WP-LESSwp-less, 0unaffected
Weakness

CWE details

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

CWE-538 · source CWE mapping

Insertion of Sensitive Information into Externally-Accessible File or Directory

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