Security readout for executives and security teams
Plain-English summary
A WordPress membership payments plugin had a missing authorization check that could let an unauthenticated attacker change the site’s Stripe payment keys. That could redirect or disrupt payment processing settings, but the public sources rate impact as limited integrity impact, not data theft or service outage.
Executive priority
Prioritize remediation for revenue-generating WordPress sites that use this plugin for Stripe payments. The issue is not rated critical, but unauthorized payment key changes can create payment disruption, misrouting risk, and incident response cost.
Technical view
CVE-2024-1389 is a CWE-862 missing authorization flaw in the Paid Membership Subscriptions plugin through version 2.11.1. The affected function is pms_stripe_connect_handle_authorization_return. CVSS 3.1 is 5.3: network exploitable, low complexity, no privileges or user interaction, unchanged scope, low integrity impact only.
Likely exposure
Exposure is limited to WordPress sites running Paid Membership Subscriptions through version 2.11.1, especially sites using Stripe payment configuration. Sites without this plugin, or running versions outside the affected range, are not indicated as affected by the provided sources.
Exploitation context
The CVE record and Wordfence description support unauthenticated modification of Stripe payment keys. The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Treat exploitation status as unconfirmed, not known exploited.
Researcher notes
The available evidence identifies the vulnerable function, missing capability check, affected range through 2.11.1, and a WordPress Trac changeset. The bundle does not provide exploit telemetry, detailed patch version naming, or proof of compromise indicators.
Mitigation direction
- Upgrade the plugin to a vendor-fixed release newer than 2.11.1.
- Check official plugin and Wordfence guidance for any additional remediation steps.
- Review Stripe settings in WordPress for unauthorized key changes.
- If keys changed unexpectedly, rotate Stripe keys and reconfigure the plugin.
- Restrict administrative access and monitor payment configuration changes.
Validation and detection
- Inventory WordPress sites for the plugin and installed version.
- Confirm no production site runs version 2.11.1 or earlier.
- Verify Stripe payment keys match approved values.
- Review logs for unexpected access to the Stripe authorization return handler.
- Confirm patched code adds authorization checks around the affected function.
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-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-2024-1389 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
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/cd5f5861-5be4-456d-915d-bafb7bff2110?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/paid-member-subscriptions/trunk/includes/gateways/stripe/admin/functions-admin-connect.php#L11CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3034497%40paid-member-subscriptions%2Ftrunk&old=3031453%40paid-member-subscriptions%2Ftrunk&sfp_email=&sfph_mail=CVE reference
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.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.