LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52129: WordPress teachPress Plugin <= 9.0.4 is vulnerable to Cross Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) vulnerability in Michael Winkler teachPress.This issue affects teachPress: from n/a through 9.0.4.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-52129 is a medium-severity CSRF issue in the WordPress teachPress plugin through version 9.0.4. An attacker would need to trick a user into interacting with malicious content while their browser is authenticated to WordPress. Business impact is limited but can include unauthorized plugin-related actions, depending on the affected functionality.

Executive priority

Treat as a normal-priority remediation item for WordPress estates using teachPress. It is not currently supported by active-exploitation evidence in the bundle, but affected sites should still be updated or the plugin removed during routine vulnerability maintenance.

Technical view

The source bundle identifies CWE-352 in Michael Winkler teachPress for WordPress, affecting versions through 9.0.4. CVSS 3.1 score is 6.3 with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, and low confidentiality, integrity, and availability impact. Specific vulnerable endpoints and fixed version are not provided.

Likely exposure

Exposure is limited to WordPress sites running the teachPress plugin at version 9.0.4 or earlier. Sites without the plugin, or with versions confirmed outside the affected range, are not indicated as affected by the bundle.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Practical abuse depends on social engineering a logged-in WordPress user and on what teachPress action lacks CSRF protection. No exploit details are provided in the sources.

Researcher notes

Evidence is sparse. The available data establishes product, affected range, CWE, CVSS, and Patchstack reference, but not vulnerable actions, exploit availability, or a named fixed version. Avoid assuming exploitability beyond CSRF requiring user interaction.

Mitigation direction

  • Inventory WordPress sites for the teachPress plugin and installed version.
  • Check vendor, WordPress plugin, or Patchstack guidance for a fixed release.
  • Update teachPress if a fixed version is available from trusted sources.
  • Disable or remove teachPress where it is not business-critical.
  • Warn WordPress admins to avoid untrusted links while authenticated.

Validation and detection

  • Confirm whether teachPress is installed on each WordPress instance.
  • Record exact teachPress versions and flag 9.0.4 or earlier.
  • Review WordPress audit logs for unexpected teachPress-related changes.
  • After updating, verify the installed version is outside the affected range.
  • Confirm no compensating control is being treated as a permanent fix.
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-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 lookup
cve · low confidence lookup

CVE-2023-52129 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.3 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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
Michael WinklerteachPressteachpress, n/aunaffected
Weakness

CWE details

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

CWE-352 · source CWE mapping

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.