LiveActive security incident?Get immediate response
CVE Record

CVE-2020-24841: PNPSCADA 2.200816204020 allows SQL injection via parameter 'interf' in /browse.jsp.

PNPSCADA 2.200816204020 allows SQL injection via parameter 'interf' in /browse.jsp. Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-24841 is a reported SQL injection in PNPSCADA 2.200816204020 through the `interf` parameter in `/browse.jsp`. If reachable and exploitable, it could let an attacker access or change application/database data. Public exploit information exists, but the provided sources do not show confirmed active exploitation.

Executive priority

Prioritize review if PNPSCADA is internet-facing or supports sensitive operational workflows. The lack of a published severity score lowers certainty, not potential impact. Public exploit information and possible database compromise make this a near-term remediation and exposure-reduction item.

Technical view

The CVE record describes SQL injection in PNPSCADA 2.200816204020, affecting `/browse.jsp` via the `interf` parameter. Impact may include application compromise, database data access or modification, and potential use of database-layer weaknesses. No CVSS, CWE, authentication requirement, or vendor fix is provided in the supplied sources.

Likely exposure

Organizations running PNPSCADA 2.200816204020 are potentially exposed, especially if the web interface is reachable from untrusted networks. Exposure depends on deployment, authentication, and network segmentation, which are not specified in the sources.

Exploitation context

A public Exploit-DB reference exists for this issue. The source bundle marks CISA KEV as false and provides no cited evidence of active exploitation. Treat public-facing instances as higher priority because SQL injection can affect sensitive operational and database data.

Researcher notes

Evidence is sparse: the supplied record names the vulnerable endpoint and parameter but omits CVSS, CWE, authentication context, and fix status. Avoid assuming broader product versions. Validate exposure safely and focus on version confirmation, reachability, logs, and vendor advisories.

Mitigation direction

  • Check PNPSCADA vendor guidance for patches, upgrades, or configuration advisories.
  • Restrict PNPSCADA web access to trusted administrative networks only.
  • Place the interface behind VPN or equivalent access controls.
  • Apply least-privilege permissions to the PNPSCADA database account.
  • Monitor application and database logs for suspicious `/browse.jsp` activity.
  • Use compensating controls such as WAF rules where appropriate.

Validation and detection

  • Inventory systems for PNPSCADA 2.200816204020.
  • Confirm whether `/browse.jsp` is accessible from untrusted networks.
  • Review application code or configuration handling the `interf` parameter.
  • Check database permissions used by the application account.
  • Review logs for unusual errors or requests involving `/browse.jsp`.
  • Verify whether vendor guidance or a newer fixed version exists.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-24841 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
1ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.