LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25321: WordPress SupportCandy plugin <= 3.4.4 - Broken Access Control vulnerability

Missing Authorization vulnerability in PSM Plugins SupportCandy supportcandy allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SupportCandy: from n/a through <= 3.4.4.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25321 is a medium-severity access-control issue in the WordPress SupportCandy plugin through version 3.4.4. A missing authorization check may let an unauthenticated attacker perform limited unauthorized changes. The available sources do not show active exploitation or a named fixed version.

Executive priority

Treat as a near-term remediation item for WordPress sites using SupportCandy. Business urgency is moderate: the issue may allow unauthorized changes, but current public evidence does not indicate data theft, service outage impact, or active exploitation.

Technical view

The issue is CWE-862 Missing Authorization in PSM Plugins SupportCandy. CVSS 3.1 is 5.3: network exploitable, low complexity, no privileges, no user interaction, unchanged scope, low integrity impact, and no confidentiality or availability impact. Affected versions are reported as SupportCandy through 3.4.4.

Likely exposure

Exposure is likely limited to WordPress sites running the SupportCandy plugin at version 3.4.4 or earlier. Sites without the plugin, or with versions outside the affected range, are not indicated as affected by the provided sources.

Exploitation context

The CVE data rates exploitation as unauthenticated over the network with low complexity. However, the provided sources do not include exploit details, proof-of-concept status, or evidence of active exploitation. It is not listed as CISA KEV in the supplied bundle.

Researcher notes

The public bundle lacks endpoint-level detail, exploit conditions, and fixed-version information. Analysis should remain version-focused and source-grounded. Avoid assuming broader WordPress exposure beyond SupportCandy through 3.4.4 until vendor or Patchstack advisories provide more specifics.

Mitigation direction

  • Inventory WordPress sites for the SupportCandy plugin and record installed versions.
  • Prioritize sites running SupportCandy version 3.4.4 or earlier.
  • Check SupportCandy, Patchstack, or WordPress plugin guidance for a patched version or vendor workaround.
  • Apply any vendor-supported update or mitigation when confirmed.
  • If no fix is available, consider temporary risk reduction for exposed support workflows.

Validation and detection

  • Confirm whether SupportCandy is installed on each WordPress instance.
  • Verify the installed plugin version against the affected range: through 3.4.4.
  • Review administrative logs for unexpected ticket or support-setting changes.
  • Monitor vendor and Patchstack pages for updated remediation details.
  • Document compensating controls where immediate update is not possible.
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-25321 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: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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
PSM PluginsSupportCandysupportcandy, 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.