LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31376: WordPress NanoSupport plugin <= 0.6.0 - Broken Access Control vulnerability

Missing Authorization vulnerability in Mayeenul Islam NanoSupport nanosupport allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects NanoSupport: from n/a through <= 0.6.0.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31376 is a broken access control issue in the WordPress NanoSupport plugin through version 0.6.0. A logged-in user may be able to perform actions they should not be authorized to perform. The public record rates impact as medium, with limited integrity impact and no stated confidentiality or availability impact.

Executive priority

Treat this as a moderate WordPress plugin exposure. Prioritize sites where NanoSupport is installed and untrusted users can log in. It does not currently justify emergency response based on the provided evidence, but it should enter normal patch and plugin-risk workflows.

Technical view

The issue is CWE-862, missing authorization, in Mayeenul Islam NanoSupport for WordPress through 0.6.0. CVSS 3.1 is 4.3: network reachable, low complexity, low privileges required, no user interaction, unchanged scope, integrity low, confidentiality and availability none.

Likely exposure

Exposure is limited to WordPress sites running the NanoSupport plugin at version 0.6.0 or earlier. The CVSS vector indicates an attacker needs a low-privileged authenticated account, so public self-registration or weak account controls increase relevance.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Public details provided here do not identify the exact vulnerable function, exploit method, fixed version, or vendor workaround.

Researcher notes

Available public metadata identifies missing authorization but not the affected endpoint or action. Validate exposure through asset inventory and permission review, not exploit reproduction. Track Patchstack and CVE updates for more precise remediation or affected-version clarification.

Mitigation direction

  • Inventory WordPress sites for NanoSupport versions 0.6.0 or earlier.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed release or workaround.
  • Disable NanoSupport where it is not business-critical until guidance is confirmed.
  • Restrict creation and retention of low-privileged WordPress accounts.
  • Review plugin permissions and administrative access for unnecessary roles.

Validation and detection

  • Confirm whether NanoSupport is installed on each WordPress site.
  • Record installed NanoSupport version and compare against 0.6.0 or earlier.
  • Check whether public registration or broad contributor accounts are enabled.
  • Review logs for unexpected NanoSupport changes by low-privileged users.
  • After remediation, confirm the plugin is updated, disabled, or otherwise addressed.
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-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-31376 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
4.3 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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
Mayeenul IslamNanoSupportnanosupport, 0unaffected
Weakness

CWE details

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

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.