LiveActive security incident?Get immediate response
CVE Record

CVE-2010-10009: frioux ptome sql injection

A vulnerability was found in frioux ptome. It has been rated as critical. This issue affects some unknown processing. The manipulation leads to sql injection. The patch is named 26829bba67858ca0bd4ce49ad50e7ce653914276. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-218519.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2010-10009 is a SQL injection issue in frioux ptome. The public record says affected versions are not identified, but a specific upstream patch commit is available. Business risk depends on whether ptome is deployed and reachable by users on an adjacent network.

Executive priority

Treat as a moderate, inventory-driven remediation item. Escalate if ptome is used in production, reachable from semi-trusted networks, or connected to sensitive databases.

Technical view

The issue is classified as CWE-89 SQL injection in frioux ptome, with CVSS 3.1 score 5.5. The vector indicates adjacent-network access, low privileges, no user interaction, unchanged scope, and low confidentiality, integrity, and availability impact. The named fix is commit 26829bba67858ca0bd4ce49ad50e7ce653914276.

Likely exposure

Exposure is limited to environments running frioux ptome. The source bundle does not identify affected versions or CPEs, so teams need repository, package, and deployment inventory to confirm whether the patched commit is present.

Exploitation context

The bundle does not cite CISA KEV listing or any confirmed active exploitation. CVSS indicates exploitation requires adjacent network access and low privileges, which lowers broad internet-scale risk but still matters in trusted or internal network environments.

Researcher notes

Key gaps are affected version detail, vulnerable code path, and exploitation evidence. The safest research path is patch-diff review and controlled validation against owned systems, without assuming product versions beyond the public CVE data.

Mitigation direction

  • Identify any deployed or forked frioux ptome instances.
  • Apply the upstream patch commit named in the CVE record.
  • If patch status is unclear, check upstream project guidance.
  • Restrict access to ptome while patch validation is pending.
  • Review database account privileges used by the application.

Validation and detection

  • Confirm deployed code includes commit 26829bba67858ca0bd4ce49ad50e7ce653914276.
  • Map all ptome deployments and forks in asset inventory.
  • Review application logs for suspicious database errors.
  • Validate input-handling fixes in authorized test environments.
  • Confirm no public route exposes vulnerable functionality unexpectedly.
Prepared
Confidence
medium
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

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-2010-10009 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

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
4Source 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
5.5CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.13.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2010-10009Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
friouxptomen/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.