LiveActive security incident?Get immediate response
CVE Record

CVE-2023-28695: WordPress VigilanTor Plugin <= 1.3.10 is vulnerable to Cross Site Scripting (XSS)

Auth. (admin+) Stored Cross-Site Scripting (XSS) vulnerability in Drew Phillips VigilanTor plugin <= 1.3.10 versions.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects WordPress sites using the VigilanTor plugin at version 1.3.10 or earlier. A logged-in administrator could store malicious script content that later runs in another user’s browser. The business risk is mainly account/session abuse or content tampering inside already-administered WordPress environments.

Executive priority

Treat this as a moderate WordPress hygiene issue. Prioritize sites with shared administrator access, agency management, or high-visibility public content, but it is not evidenced as actively exploited in the supplied sources.

Technical view

CVE-2023-28695 is an authenticated administrator-level stored XSS issue in Drew Phillips VigilanTor for WordPress, reported for versions up to 1.3.10. CVSS 3.1 is 5.9 with network access, low complexity, high privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to WordPress installations that have VigilanTor installed and enabled at version 1.3.10 or earlier. Risk is higher where many administrators, agencies, or contractors have admin access.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The vulnerability requires administrator-level access and user interaction, which materially lowers broad internet exploitation likelihood compared with unauthenticated WordPress flaws.

Researcher notes

Evidence identifies authenticated admin+ stored XSS and CVSS 5.9, but the bundle does not provide a fixed version, vulnerable parameter, proof of concept, or exploitation telemetry. Avoid assuming patch availability beyond vendor guidance.

Mitigation direction

  • Inventory WordPress sites for the VigilanTor plugin and installed version.
  • Check vendor or Patchstack guidance for any fixed version before updating.
  • Update VigilanTor if a patched release is documented by trusted sources.
  • Disable or remove VigilanTor where it is not business-critical.
  • Restrict WordPress administrator access to trusted, necessary users only.

Validation and detection

  • Confirm whether VigilanTor is installed on each WordPress site.
  • Verify whether the installed version is 1.3.10 or earlier.
  • Review administrator accounts for unnecessary, stale, or third-party access.
  • Check recent WordPress admin changes for unexpected script-like content.
  • Confirm remediation status against vendor or Patchstack documentation.
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-28695 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-28695Attack 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
Drew PhillipsVigilanTorvigilantor, 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.