LiveActive security incident?Get immediate response
CVE Record

CVE-2022-38878: School Activity Updates with SMS Notification v1.0 is vulnerable to SQL Injection via /activity/admin/modul...

School Activity Updates with SMS Notification v1.0 is vulnerable to SQL Injection via /activity/admin/modules/event/index.php?view=edit&id=.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects School Activity Updates with SMS Notification v1.0 and could let a privileged attacker manipulate database queries through an admin event-edit function. The business risk is serious because successful exploitation could expose, change, or disrupt stored application data.

Executive priority

Prioritize within the normal high-severity application security queue. Escalate faster if the application is internet-facing, stores sensitive school or user data, or has broad admin access. No source in the bundle confirms active exploitation.

Technical view

The CVE describes CWE-89 SQL injection in School Activity Updates with SMS Notification v1.0, in the event edit id parameter under the admin module. CVSS 3.1 is 7.2 with AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, meaning exploitation is network reachable but requires high privileges.

Likely exposure

Exposure is likely limited to organizations running this specific PHP application and allowing access to its admin event-management module. The CVE record’s affected vendor and product fields are marked n/a, so asset confirmation requires local inventory review.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. A public GitHub report is referenced, but the CVSS vector indicates high privileges are required before exploitation. Treat this as a serious post-authentication application risk, not confirmed internet-wide exploitation.

Researcher notes

Evidence is sparse: the CVE record identifies the route and parameter class, but affected vendor/product metadata is n/a and no patch is named. Validate against local source code and deployment exposure before assigning remediation ownership.

Mitigation direction

  • Check vendor or project guidance for an update or official fix.
  • Restrict admin module access to trusted networks and users.
  • Review admin accounts and remove unnecessary privileged access.
  • Consider retiring or replacing the application if unsupported.
  • Increase monitoring for suspicious admin database activity.

Validation and detection

  • Confirm whether School Activity Updates with SMS Notification v1.0 is deployed.
  • Identify whether the admin event-edit module is reachable.
  • Verify who has high-privilege admin access.
  • Review logs for unusual admin event-edit activity.
  • Check vendor records for patch or remediation guidance.
Prepared
Confidence
medium
Sources
3

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

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-2022-38878 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
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

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

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
0Timeline events
0ADP providers
2Source links

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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2022-38878Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
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.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.