# CVE-2019-25640: Inout Article Base CMS Lastest SQL Injection via portalLogin.php

> Unauthenticated attackers can inject SQL via portalLogin.php to extract database information or cause denial of service.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-ppx7-4jww-hqvw

## What is CVE-2019-25640?

CVE-2019-25640 is a high-severity SQL injection vulnerability in Inoutscripts Inout Article Base CMS, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Inout Article Base CMS contains SQL injection vulnerabilities that allow unauthenticated attackers to manipulate database queries through the 'p' and 'u' parameters. Attackers can inject SQL code using XOR-based payloads in GET requests to portalLogin.php to extract sensitive database information or cause denial of service through time-based attacks.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2019-25640?


## How do I fix CVE-2019-25640?

No fix has been published for CVE-2019-25640 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-25640 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25640 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25640 and fix it if it is affected.

What it is: CVE-2019-25640 is a high-severity SQL injection vulnerability in Inoutscripts Inout Article Base CMS, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25640 exists.

Affected product: Inoutscripts Inout Article Base CMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-25640/ (Markdown: https://insights.sbomify.com/CVE-2019-25640/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-25640
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-25640
- OSV: https://osv.dev/vulnerability/CVE-2019-25640

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-25640/
Summaries are generated and may contain mistakes; the official description above is the record.