LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28071: WordPress pixfort Core plugin <= 3.2.22 - Broken Access Control vulnerability

Missing Authorization vulnerability in PixFort pixfort Core pixfort-core allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects pixfort Core: from n/a through <= 3.2.22.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-28071 affects the WordPress pixfort Core plugin through version 3.2.22. It is a missing authorization issue, meaning a logged-in user may access actions or data they should not. The CVSS score is 6.3, so this is a moderate business risk, especially on sites with many user accounts.

Executive priority

Treat as a scheduled but timely remediation item. Prioritize sites with public registration, customer accounts, or many low-privileged users. There is no source-backed evidence of active exploitation, but access-control flaws can affect data integrity and trust if abused.

Technical view

The issue is categorized as CWE-862: Missing Authorization in PixFort pixfort Core. The CVSS vector indicates network access, low attack complexity, low privileges required, no user interaction, and limited confidentiality, integrity, and availability impact. The provided sources do not identify the vulnerable endpoint, exploit details, or a fixed version.

Likely exposure

Exposure is likely limited to WordPress sites running pixfort Core version 3.2.22 or earlier, especially where untrusted or low-privileged users can log in. Sites not using this plugin are not affected based on the provided sources.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV in the source bundle. The vulnerability requires an authenticated, low-privileged user, which lowers risk compared with unauthenticated flaws but remains relevant for public membership or customer portals.

Researcher notes

The public data is sparse. Sources identify the product, affected range, CWE, and CVSS only. They do not provide endpoint details, proof of exploitation, patch version, or workaround. Avoid assuming exploitability beyond the CVSS conditions: network-reachable, low privileges required, and no user interaction.

Mitigation direction

  • Inventory WordPress sites for the pixfort Core plugin and installed version.
  • Check PixFort, WordPress plugin, and Patchstack guidance for a fixed release or workaround.
  • Update pixfort Core if a vendor-supported fixed version is available.
  • Disable or remove the plugin where it is not business-critical.
  • Limit creation of untrusted WordPress user accounts until resolved.

Validation and detection

  • Confirm whether pixfort Core is installed on each WordPress site.
  • Record plugin versions and flag versions 3.2.22 or earlier.
  • Review user roles and identify sites allowing low-privileged public registration.
  • Monitor vendor and Patchstack pages for remediation details.
  • Check access logs for unusual authenticated activity if exposure exists.
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-28071 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
6.3 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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
PixFortpixfort Corepixfort-core, 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.