Security readout for executives and security teams
Plain-English summary
CVE-2026-27073 affects the WordPress plugin “Addi – Cuotas que se adaptan a ti” up to version 2.0.4. The issue involves hard-coded credentials that may allow abuse of password recovery. For businesses using this plugin, the main concern is unauthorized account or workflow manipulation. No cited source confirms active exploitation.
Executive priority
Treat as high priority for any WordPress site using this payment-related plugin. Prioritize identification, version confirmation, and vendor guidance review. If the plugin is not business-critical, consider disabling it until remediation is clear. No public source here confirms active exploitation.
Technical view
The CVE describes CWE-798, use of hard-coded credentials, in the buy-now-pay-later-addi WordPress plugin through version 2.0.4. CVSS 3.1 is 7.5: network-accessible, low complexity, no privileges, no user interaction, with high integrity impact and no stated confidentiality or availability impact.
Likely exposure
Exposure is limited to WordPress sites with the Addi buy-now-pay-later plugin installed at version 2.0.4 or earlier. The source bundle does not identify affected configurations beyond the plugin/version range. The CVE record’s affected data appears sparse, so confirm against the installed plugin metadata and vendor or Patchstack guidance.
Exploitation context
The vulnerability is remotely reachable and does not require authentication, according to the CVSS vector. The described abuse path is password recovery exploitation. The source bundle does not provide public exploit details, exploitation evidence, or CISA KEV listing, so active exploitation should not be assumed.
Researcher notes
Evidence is limited to CVE and Patchstack references. The affected product is a WordPress plugin, with CWE-798 and a password recovery exploitation description. The CVE JSON affected entry appears inconsistent with the narrative range, so validation should rely on plugin slug, installed version, and vendor/Patchstack updates.
Mitigation direction
- Inventory WordPress sites for the buy-now-pay-later-addi plugin.
- If installed, determine whether the version is 2.0.4 or earlier.
- Check Addi, WordPress.org, and Patchstack guidance for a fixed version or vendor advisory.
- Update promptly if an official fixed version is available.
- Disable or remove the plugin where business operations do not require it.
- Review password recovery and account-change activity for suspicious integrity-impacting events.
Validation and detection
- Confirm the plugin slug is buy-now-pay-later-addi.
- Record the installed plugin version from WordPress administration or asset inventory.
- Compare installed versions against the affected range: through 2.0.4.
- Check whether compensating controls restrict WordPress administrative and recovery workflows.
- Review logs for unusual password recovery, account update, or plugin-related events.
- Track vendor advisories until a definitive fix or mitigation is documented.
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-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-27073 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:H/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.