LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32390: WordPress Nanosoft theme < 1.3.2 - Broken Access Control vulnerability

Missing Authorization vulnerability in linethemes Nanosoft nanosoft allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Nanosoft: from n/a through < 1.3.2.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-32390 affects the WordPress Nanosoft theme before version 1.3.2. It is a broken access control issue that could let a logged-in user perform actions they should not be authorized to perform. Public sources rate it medium severity, with limited integrity and availability impact and no stated confidentiality impact.

Executive priority

Treat as a routine but timely WordPress maintenance issue. Prioritize sites where public registration, customer logins, or many low-privileged accounts exist, because exploitation requires authenticated access.

Technical view

The issue is CWE-862 Missing Authorization in linethemes Nanosoft for WordPress, affecting versions prior to 1.3.2. CVSS 3.1 is 5.4: network exploitable, low complexity, low privileges required, no user interaction, unchanged scope, with low integrity and availability impact.

Likely exposure

Exposure is limited to WordPress sites using the Nanosoft theme below 1.3.2. The CVSS vector indicates an attacker needs low-privileged authenticated access, reducing risk compared with unauthenticated flaws.

Exploitation context

The provided sources do not report active exploitation, and this CVE is not listed as CISA KEV in the source bundle. Public technical detail is limited, so defenders should avoid assuming specific attack paths beyond missing authorization.

Researcher notes

Available sources identify the vulnerability class, affected version range, and CVSS vector but do not describe the vulnerable endpoint, action, or proof of exploitation. Assessment should focus on version exposure and authorization boundaries without assuming unreported exploit mechanics.

Mitigation direction

  • Inventory WordPress sites for the Nanosoft theme and record installed versions.
  • Update Nanosoft to version 1.3.2 or later if available from the vendor.
  • If updating is not possible, restrict low-privileged account creation and access.
  • Monitor vendor and Patchstack guidance for confirmed remediation details.
  • Review WordPress accounts and remove unnecessary low-privileged users.

Validation and detection

  • Confirm whether Nanosoft is installed on each WordPress site.
  • Verify the installed Nanosoft version is 1.3.2 or later.
  • Check administrative logs for unusual actions by low-privileged users.
  • Review role permissions for unnecessary access to theme-related functions.
  • Track the CVE and Patchstack entry for updated technical details.
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-2026-32390 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.4 (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:L

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

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-32390Attack 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:L

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
linethemesNanosoftnanosoft, 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.