LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10753: e107 2.1.2 allows PHP Object Injection with resultant SQL injection, because usersettings.php uses unserial...

e107 2.1.2 allows PHP Object Injection with resultant SQL injection, because usersettings.php uses unserialize without an HMAC.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE concerns e107 2.1.2 and a user settings path that handled serialized PHP data unsafely. In practical terms, an attacker may be able to turn that trust mistake into database manipulation. The public bundle does not provide a CVSS score, confirmed affected CPEs, patch status, or evidence of active exploitation.

Executive priority

Give this focused asset-discovery priority rather than emergency escalation. If e107 2.1.2 is present on an internet-facing site, treat it as urgent because the described impact reaches database integrity. If no matching assets exist, record non-exposure with evidence.

Technical view

The description states that usersettings.php uses unserialize without an HMAC, allowing PHP object injection with resultant SQL injection in e107 2.1.2. KEV is false, and the supplied metadata has no CVSS, CWE, CPE, or fixed-version details. Treat product/version attribution as based on the CVE title and references.

Likely exposure

Exposure is most plausible for internet-facing e107 2.1.2 deployments or forks retaining the vulnerable usersettings.php behavior. The provided affected-product fields are listed as n/a, so asset confirmation must come from local inventory, application banners, source review, or vendor records.

Exploitation context

The bundle supports exploitability as a vulnerability class but does not support active exploitation in the wild. It references a RIPSTECH demonstration and blog post, but no KEV listing or source in the bundle confirms ongoing exploitation campaigns.

Researcher notes

The record is sparse: no CVSS, CWE, CPE, or patch metadata is supplied. The core issue is unsafe deserialization without integrity protection, with SQL injection as the stated consequence. Avoid assuming broader e107 versions are affected unless vendor or code evidence confirms it.

Mitigation direction

  • Identify any running e107 2.1.2 instances or derived codebases.
  • Check e107 vendor guidance for fixed versions or supported remediation.
  • Prioritize vendor-supported upgrade or replacement for exposed instances.
  • Reduce public exposure of affected user settings functionality until remediated.
  • Review related logs for unusual settings activity or SQL error patterns.

Validation and detection

  • Confirm application name and exact version from deployment inventory.
  • Review whether usersettings.php is present and reachable.
  • Check whether the code still uses PHP unserialize on untrusted data.
  • Verify any remediation against vendor release notes or official guidance.
  • Document evidence because source metadata lacks CPE and fixed-version details.
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.

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-2016-10753 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
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

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.