LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1542: Super Stage WP <= 1.0.1 - Unauthenticated PHP Object Injection

The Super Stage WP WordPress plugin through 1.0.1 unserializes user input via REQUEST, which could allow unauthenticated users to perform PHP Object Injection when a suitable gadget is present on the blog.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1542 affects the Super Stage WP WordPress plugin through 1.0.1. A remote unauthenticated user may trigger unsafe PHP object handling. Business risk is site compromise depending on other installed code. The public sources do not show confirmed active exploitation or a named fixed version.

Executive priority

Treat as a near-term WordPress hygiene issue, not an emergency based on available evidence. Prioritize internet-facing or business-critical WordPress sites, especially those with many plugins. Disable the plugin if not needed while awaiting clear vendor remediation guidance.

Technical view

The plugin unserializes user-controlled REQUEST input, mapped to CWE-502. This can enable unauthenticated PHP Object Injection when a suitable gadget exists in the WordPress site’s plugin/theme codebase. CVSS 3.1 is 6.5: network, low complexity, no privileges, no user interaction, with low confidentiality and integrity impact.

Likely exposure

Internet-facing WordPress sites running Super Stage WP through version 1.0.1 are potentially exposed. Risk depends on whether the plugin is active and whether exploitable gadget classes are present from WordPress, themes, or other plugins.

Exploitation context

The vulnerability is remotely reachable without authentication according to the CVSS vector and description. The source bundle does not establish in-the-wild exploitation, and CISA KEV status is false. Exploitability may require a compatible gadget chain on the affected site.

Researcher notes

Public data is limited. The CVE title states Super Stage WP <= 1.0.1, while the affected metadata is sparse and vendor is unknown. No fixed version is named in the provided sources. Confirm plugin presence and avoid assuming exploitability without a gadget chain assessment.

Mitigation direction

  • Identify WordPress sites using Super Stage WP and record plugin versions.
  • Disable or remove Super Stage WP where it is not business-critical.
  • Check vendor, WordPress plugin, and WPScan guidance for a fixed release.
  • Reduce unnecessary plugins and themes to limit available gadget chains.
  • Monitor affected sites for unusual unauthenticated requests and file changes.

Validation and detection

  • Confirm whether Super Stage WP is installed and active on each WordPress site.
  • Verify whether the installed version is 1.0.1 or earlier.
  • Review plugin/theme inventory for unnecessary components that expand gadget exposure.
  • Check security monitoring for suspicious requests around the plugin timeframe.
  • Document remediation status and recheck after vendor guidance is applied.
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-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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-1542 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.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UnknownSuper Stage WP0unknown
Weakness

CWE details

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

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.