LiveActive security incident?Get immediate response
CVE Record

CVE-2025-70152: code-projects Community Project Scholars Tracking System 1.0 is vulnerable to SQL Injection in the admin us...

code-projects Community Project Scholars Tracking System 1.0 is vulnerable to SQL Injection in the admin user management endpoints /admin/save_user.php and /admin/update_user.php. These endpoints lack authentication checks and directly concatenate user-supplied POST parameters (firstname, lastname, username, password, user_id) into SQL queries without validation or parameterization.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Scholars Tracking System 1.0 allows unauthenticated users to submit data that is inserted directly into database queries. If vulnerable administration endpoints are reachable, an attacker could potentially read, alter, or destroy sensitive records without credentials or user interaction.

Executive priority

Treat confirmed reachable deployments as an immediate remediation priority. Temporarily isolate them if a verified fix is unavailable. Also initiate log review and compromise assessment because successful abuse could affect the full database, although active exploitation has not been established.

Technical view

CVE-2025-70152 is a CWE-89 SQL injection in /admin/save_user.php and /admin/update_user.php. The endpoints reportedly lack authentication and concatenate supplied POST fields into SQL statements without validation or parameterization. CVSS 3.1 rates it 9.8 because exploitation is network-accessible, low-complexity, unauthenticated, and potentially compromises confidentiality, integrity, and availability.

Likely exposure

Exposure is limited to deployments of code-projects Scholars Tracking System 1.0 containing the named endpoints. Risk is greatest where they are internet-accessible. The supplied CVE data provides no reliable package identifiers, deployment prevalence, or affected-version range beyond 1.0, so organizations should verify installations manually.

Exploitation context

The supplied record is not listed in CISA KEV and contains no evidence of active exploitation. Public researcher write-ups exist, increasing awareness, but that alone does not establish exploitation in the wild. The missing authentication and network-accessible injection condition make vulnerable deployments attractive targets.

Researcher notes

The source bundle identifies five concatenated parameters: firstname, lastname, username, password, and user_id. Validate both endpoints independently because authentication and query construction are separate control failures. Public metadata lacks CPEs, a confirmed patch version, and deployment prevalence; avoid extending affected-product claims beyond Scholars Tracking System 1.0.

Mitigation direction

  • Identify and restrict access to the affected administration endpoints immediately.
  • Remove vulnerable deployments from public access until remediation is verified.
  • Replace SQL string concatenation with parameterized queries for every supplied field.
  • Require authenticated, authorized administration access before processing requests.
  • Check the project publisher and CVE record for confirmed remediation guidance.
  • Rotate exposed application or database credentials if compromise is suspected.

Validation and detection

  • Inventory deployments and confirm whether version 1.0 contains both named PHP files.
  • Verify unauthenticated requests are rejected before any database operation occurs.
  • Review source code to confirm all affected queries use parameterized statements.
  • Inspect web and database logs for unusual POST activity targeting these endpoints.
  • Test authorization and SQL-injection regressions in a controlled environment after remediation.
Prepared
Confidence
high
Sources
5

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.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
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-2025-70152 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N

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.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N3.95.9mitre

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-70152Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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