LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25409: WordPress JAMstack Deployments plugin <= 1.1.1 - Broken Access Control vulnerability

Missing Authorization vulnerability in crgeary JAMstack Deployments wp-jamstack-deployments allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects JAMstack Deployments: from n/a through <= 1.1.1.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-25409 affects the WordPress JAMstack Deployments plugin through version 1.1.1. It is a broken access control issue: an authenticated user may be able to perform an action they should not be authorized to perform. Business impact appears limited to integrity, not data theft or service outage, based on the published CVSS details.

Executive priority

Prioritize for WordPress environments using this plugin, especially multi-user sites. This is not currently evidenced as actively exploited, but it can allow unauthorized changes by authenticated users. Address during the next normal vulnerability remediation cycle, sooner for business-critical publishing or deployment workflows.

Technical view

The issue is CWE-862 Missing Authorization in crgeary wp-jamstack-deployments. CVSS 3.1 is 4.3: AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N. Sources identify affected versions as JAMstack Deployments through <= 1.1.1. The public bundle does not provide endpoint-level details, exploit procedure, or a named fixed version.

Likely exposure

Exposure is limited to WordPress sites where the JAMstack Deployments plugin is installed at version 1.1.1 or earlier. The CVSS vector indicates exploitation requires low privileges, so risk is higher on sites with many authenticated users, weak account governance, or compromised contributor accounts.

Exploitation context

The source bundle does not show CISA KEV listing or cite active exploitation. The vulnerability is network-reachable, low-complexity, and requires authentication. Public details are sparse, so treat it as a permissions-control flaw rather than evidence of broad exploitation.

Researcher notes

Evidence is limited to the CVE data and Patchstack reference. The affected range is stated as through <= 1.1.1, but the bundle does not include a fixed version or technical proof details. Avoid assuming unauthenticated access, confidentiality impact, or availability impact beyond the published CVSS vector.

Mitigation direction

  • Inventory WordPress sites for JAMstack Deployments plugin version 1.1.1 or earlier.
  • Check the plugin vendor and Patchstack entry for an updated or patched release.
  • If no fix is available, disable the plugin where business impact is acceptable.
  • Limit WordPress accounts with access to deployment-related plugin functions.
  • Review low-privilege accounts and remove unnecessary authenticated users.

Validation and detection

  • Confirm whether wp-jamstack-deployments is installed on each WordPress instance.
  • Record installed plugin versions and flag 1.1.1 or earlier.
  • Review WordPress roles with access to deployment or plugin management functions.
  • Check logs for unexpected deployment configuration or trigger activity.
  • Recheck vendor advisories before closing remediation as complete.
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-25409 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-2026-25409Attack 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
crgearyJAMstack Deploymentswp-jamstack-deployments, 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.