LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52430: The caddy-security plugin 1.1.20 for Caddy allows reflected XSS via a GET request to a URL that contains an...

The caddy-security plugin 1.1.20 for Caddy allows reflected XSS via a GET request to a URL that contains an XSS payload and begins with either a /admin or /settings/mfa/delete/ substring.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-52430 is a reflected cross-site scripting issue in caddy-security plugin 1.1.20 for Caddy. A user with some privileges must be tricked into opening a crafted link. Successful exploitation could let attacker-controlled script run in the victim’s browser session, risking limited data exposure or unauthorized actions.

Executive priority

Treat this as a targeted web security issue, not an internet-wide emergency. Prioritize environments exposing caddy-security administrative workflows, especially where administrators access them from normal browsing sessions.

Technical view

The CVE describes CWE-79 reflected XSS triggered by GET requests whose URL begins with /admin or /settings/mfa/delete/. CVSS 3.1 is 5.4: network reachable, low complexity, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is most likely where caddy-security plugin 1.1.20 is deployed and its administrative or MFA settings paths are reachable to logged-in users. The CVE affected-product metadata is incomplete, so teams should confirm installed plugin versions directly.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates exploitation requires an authenticated or low-privileged context plus user interaction, such as persuading a target to open a malicious link.

Researcher notes

Evidence identifies caddy-security plugin 1.1.20 and two affected path prefixes, but the CVE affected-product fields are n/a. No source in the bundle confirms active exploitation, broad version ranges, or a specific patched release.

Mitigation direction

  • Identify all Caddy deployments using the caddy-security plugin.
  • Check whether version 1.1.20 is installed anywhere.
  • Review vendor issue and Trail of Bits guidance for fixed versions or configuration advice.
  • Restrict access to administrative and MFA settings paths where possible.
  • Warn administrators not to open untrusted links while authenticated.

Validation and detection

  • Inventory plugin versions across production, staging, and container images.
  • Confirm whether affected /admin and MFA settings paths are externally reachable.
  • Review access logs for unusual encoded input targeting those path prefixes.
  • Use safe staging validation to confirm output encoding behavior.
  • Track the GitHub issue for vendor-confirmed remediation status.
Prepared
Confidence
high
Sources
4

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-52430 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.4 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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
n/an/an/aListed
Weakness

CWE details

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