CVE-2013-2122
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Edit Limit module 7.x-1.x before 7.x-1.3 for Drupal does not properly restrict access to comments, which allows remote authenticated users with the "edit comments" permission to edit arbitrary comments of other users via unspecified vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Edit Limit Drupal module 7.x-1.x before 7.x-1.3 contains an access control bypass where the module fails to properly restrict comment editing permissions. Authenticated users with the 'edit comments' permission can edit arbitrary comments belonging to other users, violating the intended access control boundaries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.x-1.0= 7.x-1.1= 7.x-1.2= 7.x-1.xCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Edit Limit module is installedNavigate to Drupal admin panel: Reports > Status report > Expand 'PHP' or check module list at Extend/Modules page. Look for 'Edit Limit' or 'Quade Edit Limit' in the list of installed modules.Affected if Edit Limit module appears in the installed modules list
-
Determine installed version of Edit LimitAt Modules page, find Edit Limit and note the version number displayed (e.g., 7.x-1.0, 7.x-1.1, 7.x-1.2). Alternatively, check the module's .info file in the module directory for the 'version' field.Affected if Version is 7.x-1.0, 7.x-1.1, 7.x-1.2, or any 7.x-1.x version before 7.x-1.3
-
Confirm 'edit comments' permission existsNavigate to People > Permissions (or Administration > People > Permissions). Locate the 'Edit Limit' section or search for 'edit comments' permission in the permissions table.Affected if The 'edit comments' permission exists and is visible in the permissions configuration
-
Check if users have 'edit comments' permissionIn the same Permissions page, look for granted checkmarks under the 'edit comments' permission for any user roles (authenticated users, editors, etc.). Also verify at People > List if any roles with this permission are assigned to users.Affected if Any user role has the 'edit comments' permission enabled and that role is assigned to at least one user
A user is affected if the Edit Limit module version is 7.x-1.2 or earlier AND any authenticated user role has been granted the 'edit comments' permission, allowing unauthorized comment editing.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Edit Limit module to version 7.x-1.3 or later which contains the proper access restriction fix. Review user permissions afterward to ensure only intended users have edit access.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2122 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-2122 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data