● High · CVSS 7.5

How to Fix CVE-2026-27073: Hard-coded Credentials in Addi, Cuotas que se adaptan a ti

Q: Is CVE-2026-27073 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-27073?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Addi, Cuotas que se adaptan a ti run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-28724: Incorrect authorization in Acronis Cyber Protect 17 — Incorrect authorization in Acronis Cyber Protect 17
How to Fix CVE-2026-27853: DNSdist (Bundle Sibling) — DNSdist (Bundle Sibling)
How to Fix CVE-2026-22407: Critical Vulnerability in Roam , Critical Vulnerability in Roam
How to Fix CVE-2026-2331: Cwe-552 files or directories accessible to external parties in SICK Lector85x , Cwe-552 files or directories accessible to external parties in SICK Lector85x
How to Fix CVE-2026-2664: Out-of-bounds read in Docker Desktop , Out-of-bounds read in Docker Desktop

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 7.5 - High
Actively exploited?	Not currently listed in CISA KEV
Affected	0 <= 2.0.4
Fixed in	See vendor advisory
Type (CWE)	CWE-798: Use of Hard-coded Credentials

What is CVE-2026-27073?

CVE-2026-27073 is a hard-coded credentials issue in Addi, Cuotas que se adaptan a ti. The product ships with a built-in account or key that anyone with a copy of the software can recover and use to log in. Vendor description: Use of Hard-coded Credentials vulnerability in Addi Addi, Cuotas que se adaptan a ti buy-now-pay-later-addi allows Password Recovery Exploitation.This issue affects Addi, Cuotas que se adaptan a ti: from n/a through <= 2.0.4.

Why this CVE matters

Hard-coded credentials are the lowest-effort path to compromise. Once the secret is reverse-engineered out of the firmware or source, every deployment of the same version is reachable by anyone with the advisory text.

For deployments of Addi, Cuotas que se adaptan a ti that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Addi, Cuotas que se adaptan a ti: 0 <= 2.0.4

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open Addi, Cuotas que se adaptan a ti's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-27073

Read the vendor advisory in full: https://patchstack.com/database/Wordpress/Plugin/buy-now-pay-later-addi/vulnerability/wordpress-addi-cuotas-que-se-adaptan-a-ti-plugin-2-0-4-broken-authentication-vulnerability?_s_id=cve
Upgrade Addi, Cuotas que se adaptan a ti to the patched build listed in the vendor advisory.
Back up the configuration (and database, where applicable) before upgrading.
Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
Restart the affected service so the patched binary loads, then verify the new version (see verification section).

The commands below are runnable starting points. Adapt the package name, target version, and host paths to your environment using the vendor advisory linked under References.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade addicuotasqueseadaptanati
dpkg -s addicuotasqueseadaptanati | grep -i version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh addicuotasqueseadaptanati -y
rpm -q addicuotasqueseadaptanati

Container image


# Vendor advisory: https://patchstack.com/database/Wordpress/Plugin/buy-now-pay-later-addi/vulnerability/wordpress-addi-cuotas-que-se-adaptan-a-ti-plugin-2-0-4-broken-authentication-vulnerability?_s_id=cve
docker pull <your-registry>/addicuotasqueseadaptanati:<patched-tag>
docker build -t <your-app>:patched .
docker stop <your-app> && docker rm <your-app>
docker run -d --name <your-app> <your-app>:patched

PowerShell detect/upgrade/verify/log (Windows)


# CVE-2026-27073 remediation runner. Adapt version checks to your environment.
$log = "C:\Logs\CVE-2026-27073-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }

try {
    Write-Log "Detect: checking installed product"
    $installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
        Where-Object { $_.Name -match 'Addi – Cuotas que se adaptan a ti' }
    if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
    Write-Log "Found version $($installed.Version)"

    Write-Log "Backup: copying program files and registry hive"
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\CVE-2026-27073-$stamp"
    New-Item -ItemType Directory -Force -Path $backup | Out-Null
    Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
    reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null

    Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
    Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue

    Write-Log "Verify: re-reading product version"
    $after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'Addi – Cuotas que se adaptan a ti' }
    Write-Log "Post-patch version: $($after.Version)"
    if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged; check vendor advisory" }
} catch {
    Write-Log "ERROR: $_"
    throw
}

Bash detect/upgrade/verify/log (Linux)


#!/usr/bin/env bash
# CVE-2026-27073 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-27073-fix.log; }

log "Detect: current addicuotasqueseadaptanati version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' addicuotasqueseadaptanati 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' addicuotasqueseadaptanati 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current"

log "Backup: snapshotting config"
backup="/var/backups/cve-2026-27073-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/addicuotasqueseadaptanati ] && cp -a /etc/addicuotasqueseadaptanati "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade addicuotasqueseadaptanati
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y addicuotasqueseadaptanati
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y addicuotasqueseadaptanati
fi

log "Verify: re-reading addicuotasqueseadaptanati version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' addicuotasqueseadaptanati)
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' addicuotasqueseadaptanati)
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: addicuotasqueseadaptanati upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-27073.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in Addi, Cuotas que se adaptan a ti, scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation.

Frequently asked questions

Is CVE-2026-27073 being exploited in the wild?