Security readout for executives and security teams
Plain-English summary
This is a medium-severity CSRF issue in a WordPress plugin used to customize permalinks. An attacker may be able to trick a site user into making an unintended change, but the public sources only support low integrity impact, not data theft or outage.
Executive priority
Handle in normal vulnerability-management cadence, faster for externally important WordPress sites or sites with frequent administrative access. The issue is not currently supported as actively exploited, but it can affect site integrity if the vulnerable plugin is present.
Technical view
CVE-2023-45103 is CWE-352 in YAS Global Team Permalinks Customizer for WordPress, reported for versions <= 2.8.2. CVSS 3.1 is 4.3 with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, and low integrity impact only.
Likely exposure
Exposure applies to WordPress sites with the Permalinks Customizer plugin installed and running a vulnerable version at or below 2.8.2. The bundle does not provide CPEs or deployment prevalence, so ownership must be confirmed from site inventories.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates the attacker needs user interaction but no account. Treat this as a targeted web-administration risk until vendor or threat-intelligence sources say otherwise.
Researcher notes
Evidence is narrow: public metadata identifies CSRF, affected plugin, <=2.8.2, CVSS, and Patchstack reference. It does not include request details, affected actions, exploit proof, or a named fixed version in the provided bundle. Avoid assuming impact beyond low integrity.
Mitigation direction
- Inventory WordPress sites for the Permalinks Customizer plugin.
- Identify any installed version at or below 2.8.2.
- Check vendor, WordPress, or Patchstack guidance for a confirmed fixed release.
- Update, disable, or remove the plugin based on business need and vendor guidance.
- Prioritize sites where administrators routinely work in browser sessions.
Validation and detection
- Confirm plugin name and version from WordPress administration or asset inventory.
- Check whether the plugin is active on public production sites.
- Review change logs or vendor notices for a CSRF fix reference.
- Verify remediation by confirming the vulnerable plugin version is no longer active.
- Monitor vendor advisories for any later exploitation or fix details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-352: 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 lookupCVE-2023-45103 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.