CVE-2020-25751: The paGO Commerce plugin 2.5.9.0 for Joomla! allows SQL Injection via the administrator/index.php?option=com_p

This month

HIGH 8.8DOWNGRADE

CVE-2020-25751 is a high-severity flaw (CVSS 8.8) affecting pago commerce. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The paGO Commerce plugin 2.5.9.0 for Joomla! allows SQL Injection via the administrator/index.php?option=com_pago&view=comments filter_published parameter.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.8% (top 21%)
CISA exploited list	No
Weakness	CWE-89
Published	2020-09-18
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: corephp

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-09-18 04:15 UTCPublished CVE record published
2026-06-17 03:07 UTCUpdated Record last modified

corephp pago commerce DOWNGRADE

Affected: 2.5.9.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.5.9.0

1. Check installed version

apt-cache policy pago-commerce || rpm -q pago-commerce || pago-commerce --version

2. No fixed release: DOWNGRADE to a release before 2.5.9.0 (Debian / Ubuntu)

apt-cache madison pago-commerce sudo apt install pago-commerce=<VERSION_BEFORE_2.5.9.0> sudo apt-mark hold pago-commerce

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list pago-commerce sudo dnf downgrade pago-commerce-<VERSION_BEFORE_2.5.9.0> sudo dnf versionlock add pago-commerce

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-25751?

pago commerce: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-25751 being exploited?

CVE-2020-25751 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-25751 affect?

CVE-2020-25751 affects pago commerce. Severity is high (CVSS 8.8). The paGO Commerce plugin 2.5.9.0 for Joomla! allows SQL Injection via the administrator/index.php?option=com_pago&view=comments filter_published parameter.

How urgent is CVE-2020-25751?

Priority 56/100. High severity; Public exploit reference

Software pages

Joomla vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs