LiveActive security incident?Get immediate response
CVE Record

CVE-2007-10001: web-cyradm search.php sql injection

A vulnerability classified as problematic has been found in web-cyradm. This affects an unknown part of the file search.php. The manipulation of the argument searchstring leads to sql injection. It is recommended to apply a patch to fix this issue. The identifier VDB-217449 was assigned to this vulnerability.

LowCVSS 3.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2007-10001 is a low-severity SQL injection issue in web-cyradm involving the search.php searchstring argument. The available sources indicate limited confidentiality impact, required low privileges, and adjacent-network access. A patch is referenced, but affected versions are not identified in the provided data.

Executive priority

Treat this as a routine remediation item unless web-cyradm is exposed beyond trusted administrative users. The risk is constrained by low CVSS severity and required privileges, but patching is still appropriate because SQL injection can expose data.

Technical view

The issue is classified as CWE-89 SQL injection in web-cyradm search.php. The CVSS 3.1 vector is AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, meaning low-complexity abuse by a low-privileged user with adjacent access, with limited confidentiality impact only.

Likely exposure

Exposure appears limited to organizations running web-cyradm where search.php is reachable by low-privileged users on an adjacent network. The source bundle does not identify affected versions, CPEs, or deployment configurations, so asset owners must map their installed code to the referenced patch.

Exploitation context

The bundle does not cite CISA KEV listing or active exploitation. VulDB describes the issue and references permissions-related signature material, but the provided sources do not establish real-world exploitation, public weaponization, or broad internet exposure.

Researcher notes

Key uncertainty is version scope: the bundle lists web-cyradm but no affected versions or CPEs. Keep analysis tied to search.php and searchstring. Do not infer impact beyond limited confidentiality because CVSS lists no integrity or availability impact.

Mitigation direction

  • Apply the referenced upstream patch or a vendor release containing it.
  • Review vendor guidance to determine affected and fixed web-cyradm versions.
  • Restrict web-cyradm access to trusted administrative networks and users.
  • Monitor application and database logs for suspicious search activity or SQL errors.

Validation and detection

  • Inventory web-cyradm deployments and confirm whether search.php is present.
  • Compare deployed code against the referenced patch commit.
  • Confirm access to web-cyradm is limited to intended users and networks.
  • Review logs for anomalous search requests or database error patterns.
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-2007-10001 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
Low
CVSS
3.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/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
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
3.5CVSS 3.1LowCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.5Low
CVSS 3.1 vector shape for CVE-2007-10001Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aweb-cyradmn/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.