LiveActive security incident?Get immediate response
CVE Record

CVE-2011-3667: The User.offer_account_by_email WebService method in Bugzilla 2.x and 3.x before 3.4.13, 3.5.x and 3.6.x be...

The User.offer_account_by_email WebService method in Bugzilla 2.x and 3.x before 3.4.13, 3.5.x and 3.6.x before 3.6.7, 3.7.x and 4.0.x before 4.0.3, and 4.1.x through 4.1.3, when createemailregexp is not empty, does not properly handle user_can_create_account settings, which allows remote attackers to create user accounts by leveraging a token contained in an e-mail message.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This Bugzilla flaw could let an outside party create an account even when account creation was meant to be restricted. It requires a specific Bugzilla configuration involving email-based account offers. The business risk is unwanted access to issue-tracking data and workflows, especially where Bugzilla contains sensitive engineering or security tickets. Exposure is most likely for organizations still running the listed legacy Bugzilla versions with createemailregexp configured. Publicly reachable Bugzilla instances increase concern. Systems on fixed releases, without Bugzilla, or without this email-based account creation configuration are less likely exposed. Treat as a targeted legacy exposure issue. Prioritize if Bugzilla is internet-facing or holds sensitive engineering, customer, or security information. The urgency is lower than active-exploitation cases, but unsupported or unpatched Bugzilla should be corrected promptly. Mitigation focus: Upgrade affected Bugzilla versions to the vendor-fixed releases named in the advisory.; Review Bugzilla account creation settings, especially createemailregexp and user_can_create_account.; Restrict access to legacy Bugzilla instances until upgrade or configuration review is complete..

Prepared

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

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-2011-3667 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.