CVE-2005-1932 json
Lpanel 1.59 and earlier, and other versions before 1.597, allows remote authenticated users to modify certain critical variables and (1) mo…
published 2005-06-30 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-1934
- cvss
- 2.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
Lpanel 1.59 and earlier, and other versions before 1.597, allows remote authenticated users to modify certain critical variables and (1) modify DNS settings for arbitrary domains via the domain parameter to diagnose.php, (2) close, open, or respond to arbitrary support tickets via the close, open, or pid parameter to view_ticket.php, (3) obtain sensitive information on arbitrary invoices via the inv parameter to viewreceipt.php, or (4) modify domain information for arbitrary domains via the editdomain parameter to domains.php.
Patch / fix
Exploit prediction
0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:P/A:N |
References
-
securityfocus.com
/bid/13869
vdb-entry, patch
-
lists.grok.org.uk
/pipermail/full-disclosure/2005-June/034417.html
mailing-list, vendor-advisory
-
lists.grok.org.uk
/pipermail/full-disclosure/2005-June/034418.html
mailing-list, vendor-advisory
-
secunia.com
/advisories/15589/
third-party-advisory, vendor-advisory
-
lists.grok.org.uk
/pipermail/full-disclosure/2005-June/034415.html
mailing-list, vendor-advisory
-
lists.grok.org.uk
/pipermail/full-disclosure/2005-June/034416.html
mailing-list, vendor-advisory
-
lists.grok.org.uk
/pipermail/full-disclosure/2005-June/034414.html
mailing-list, vendor-advisory
-
lists.grok.org.uk
/pipermail/full-disclosure/2005-June/034419.html
mailing-list
- lpanel.net /changelog.php
Sources
- CVE List CVE-2005-1932
- NVD CVE-2005-1932
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.