LiveActive security incident?Get immediate response
CVE Record

CVE-2023-26534: WordPress WP Repost Plugin <= 0.1 is vulnerable to Cross Site Scripting (XSS)

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in OneWebsite WP Repost plugin <= 0.1 versions.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a stored cross-site scripting issue in the WordPress WP Repost plugin through version 0.1. It requires an authenticated administrator-level user and another user interaction, so broad external compromise is not indicated, but affected sites should still treat it as a plugin security defect.

Executive priority

Handle during normal vulnerability remediation unless the plugin is internet-facing on high-value WordPress sites or administrator accounts are weakly controlled. Prioritize removal or vendor-confirmed remediation because the source bundle does not name a patch.

Technical view

CVE-2023-26534 is CWE-79 stored XSS in OneWebsite WP Repost <=0.1. CVSS 3.1 is 5.9 with network access, low complexity, high privileges required, user interaction required, and changed scope with limited confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to WordPress sites running OneWebsite WP Repost version 0.1 or earlier. The source bundle does not provide CPEs or a clear patched version, so asset validation must confirm plugin presence and version directly.

Exploitation context

The bundle does not report active exploitation, and the CVE is not marked KEV. Exploitation requires admin-level authentication and user interaction, which materially limits likely opportunistic exploitation compared with unauthenticated WordPress bugs.

Researcher notes

Evidence is narrow: the CVE description and Patchstack reference identify authenticated admin+ stored XSS in WP Repost <=0.1, but the bundle lists affected versions as n/a and provides no CPEs or explicit fixed version. Avoid assuming unauthenticated reachability or active exploitation.

Mitigation direction

  • Inventory WordPress sites for the wp-repost plugin and confirm installed versions.
  • Disable or remove WP Repost where it is unnecessary or unmaintained.
  • Check Patchstack and vendor guidance for any fixed release or recommended workaround.
  • Restrict administrator accounts to trusted users with MFA enabled.
  • Keep WordPress core, themes, and plugins current through normal change control.

Validation and detection

  • Review WordPress plugin inventories for OneWebsite WP Repost version 0.1 or earlier.
  • Confirm whether the vulnerable plugin is active on production sites.
  • Check administrator account lists for unnecessary or stale privileged users.
  • Review recent plugin configuration changes for unexpected administrative activity.
  • Run an authenticated vulnerability scan that detects vulnerable WordPress plugins.
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-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-2023-26534 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.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L1.73.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2023-26534Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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
OneWebsiteWP Repostwp-repost, n/aunaffected
Weakness

CWE details

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

CWE-79 · source CWE mapping

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.