CVE-2015-10054: A vulnerability, which was classified as critical, was found in githuis P2Manage

Q: How do I fix CVE-2015-10054?

p2manage: upgrade to 2015-05-15. Exact commands for each OS are on this page.

Q: Is CVE-2015-10054 being exploited?

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

Q: What does CVE-2015-10054 affect?

CVE-2015-10054 affects p2manage. Severity is medium (CVSS 5.5). A vulnerability, which was classified as critical, was found in githuis P2Manage. This affects the function Execute of the file PTwoManage/Database.cs. The manipulation of the argument sql leads to sql injection. The identifier of the patch

Q: How urgent is CVE-2015-10054?

Priority 33/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2015-10054 is a medium-severity flaw (CVSS 5.5) affecting p2manage. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability, which was classified as critical, was found in githuis P2Manage. This affects the function Execute of the file PTwoManage/Database.cs. The manipulation of the argument sql leads to sql injection. The identifier of the patch is 717380aba80002414f82d93c770035198b7858cc. It is recommended to apply a patch to fix this issue. The identifier VDB-218397 was assigned to this vulnerability.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-89
Published	2023-01-16
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: p2manage project

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

Am I affected?

Timeline

2023-01-16 18:15 UTCPublished CVE record published
2026-06-17 00:21 UTCUpdated Record last modified

p2manage project p2manage UPGRADE

Affected: < 2015-05-15

Fixed in: 2015-05-15

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy p2manage || rpm -q p2manage || p2manage --version

2. UPGRADE to 2015-05-15 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade p2manage

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade p2manage

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2015-10054?

p2manage: upgrade to 2015-05-15. Exact commands for each OS are on this page.

Is CVE-2015-10054 being exploited?

CVE-2015-10054 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-2015-10054 affect?

CVE-2015-10054 affects p2manage. Severity is medium (CVSS 5.5). A vulnerability, which was classified as critical, was found in githuis P2Manage. This affects the function Execute of the file PTwoManage/Database.cs. The manipulation of the argument sql leads to sql injection. The identifier of the patch

How urgent is CVE-2015-10054?

Priority 33/100. No elevated risk signals yet.

References

← Back to latest CVEs