LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32441: SQL Injection vulnerability in Exponent-CMS v.2.6.0 fixed in 2.7.0 allows attackers to gain access to sensi...

SQL Injection vulnerability in Exponent-CMS v.2.6.0 fixed in 2.7.0 allows attackers to gain access to sensitive information via the selectValue function in the expConfig class.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-32441 is a SQL injection in Exponent-CMS 2.6.0. A remote unauthenticated attacker could use it to read sensitive information from the database. The provided CVE data says it was fixed in version 2.7.0.

Executive priority

Prioritize remediation for any internet-facing Exponent-CMS 2.6.0 deployment. The business risk is unauthorized access to sensitive database information, with no user interaction required. If the system is internal-only, urgency depends on network access controls and data sensitivity.

Technical view

The issue is CWE-89 SQL injection in the selectValue function of the expConfig class. CVSS 3.1 is 7.5: network exploitable, low complexity, no privileges, no user interaction, with high confidentiality impact and no listed integrity or availability impact.

Likely exposure

Exposure is likely limited to organizations running Exponent-CMS 2.6.0. The structured affected-product data in the bundle is incomplete, so version confirmation should come from asset inventory, application source, deployment metadata, or vendor project records.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle. Public references include a GitHub issue and researcher write-up, but the bundle does not provide evidence of active exploitation. Treat internet-facing Exponent-CMS 2.6.0 as higher priority because exploitation is remote and unauthenticated.

Researcher notes

The main evidence identifies SQL injection in expConfig::selectValue and a fix in 2.7.0. The affected metadata is sparse, so avoid expanding scope beyond Exponent-CMS 2.6.0 without additional vendor confirmation. No KEV listing or active exploitation evidence is included.

Mitigation direction

  • Upgrade Exponent-CMS 2.6.0 to version 2.7.0 where feasible.
  • Check the Exponent-CMS project guidance for any additional hardening or migration notes.
  • Restrict public access to vulnerable instances until remediation is complete.
  • Review database and application logs for unusual read activity.
  • Back up the application and database before applying version changes.

Validation and detection

  • Inventory all Exponent-CMS deployments and confirm exact versions.
  • Confirm no production instance remains on Exponent-CMS 2.6.0.
  • Review code or package metadata to verify the upgraded release is deployed.
  • Check web server and application logs for suspicious requests around configuration handling.
  • Validate that sensitive data access logs show no unexplained bulk reads.
Prepared
Confidence
medium
Sources
4

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-2021-32441 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A: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
0Timeline events
0ADP providers
3Source 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.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-32441Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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.