LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1099: Administrative Shortcodes <= 0.3.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'login' and 'logout' Shortcode Attributes

The Administrative Shortcodes plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'login' and 'logout' shortcode attributes in all versions up to, and including, 0.3.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

MediumCVSS 6.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1099 affects the Administrative Shortcodes WordPress plugin through version 0.3.4. A logged-in user with Contributor or higher permissions could place malicious script in certain shortcode attributes. That script may run when someone views the affected page, potentially exposing session data or enabling actions in the viewer’s browser.

Executive priority

Treat as a moderate-priority WordPress application risk. Prioritize sites with many content contributors, external authors, or high-value administrator accounts. No active exploitation is cited, but stored XSS can become serious if privileged users view injected content.

Technical view

The issue is stored cross-site scripting in the plugin’s 'login' and 'logout' shortcode attributes, caused by insufficient input sanitization and output escaping. It is classified as CWE-79 with CVSS 3.1 score 6.4. Exploitation requires authenticated Contributor-level access or higher, with script execution triggered when an injected page is accessed.

Likely exposure

WordPress sites using Administrative Shortcodes versions up to and including 0.3.4 are potentially exposed, especially if untrusted users have Contributor-level access or higher.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The attacker must already have an eligible WordPress account, but stored XSS can affect later page viewers, including privileged users.

Researcher notes

Evidence indicates vulnerable code paths in plugin source around the referenced shortcode handling. The provided bundle does not identify a fixed version. Avoid assuming patch availability; verify directly with WordPress plugin or vendor guidance before closing remediation.

Mitigation direction

  • Identify sites using Administrative Shortcodes and confirm installed version.
  • If version is 0.3.4 or earlier, check vendor guidance for an update or remediation.
  • Temporarily disable or remove the plugin if business use is not required.
  • Restrict Contributor-level access to trusted users only.
  • Review content using 'login' and 'logout' shortcodes for suspicious attributes.

Validation and detection

  • Inventory WordPress plugins across managed sites.
  • Confirm whether Administrative Shortcodes is installed and at version 0.3.4 or earlier.
  • Review pages and posts containing affected shortcodes.
  • Audit users with Contributor, Author, Editor, or Administrator roles.
  • Monitor for unexpected script execution reports on affected pages.
Prepared
Confidence
high
Sources
5

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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-1099 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.4 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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
shazdehAdministrative Shortcodes0unaffected
Weakness

CWE details

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