LiveActive security incident?Get immediate response
CVE Record

CVE-2021-4275: katlings pyambic-pentameter cross-site request forgery

A vulnerability, which was classified as problematic, was found in katlings pyambic-pentameter. Affected is an unknown function. The manipulation leads to cross-site request forgery. It is possible to launch the attack remotely. The name of the patch is 974f21aa1b2527ef39c8afe1a5060548217deca8. It is recommended to apply a patch to fix this issue. VDB-216498 is the identifier assigned to this vulnerability.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-4275 is a cross-site request forgery issue in katlings pyambic-pentameter. A remote attacker could potentially trick a user into making an unintended state-changing request. The published impact is limited to low integrity impact, with no confidentiality or availability impact stated.

Executive priority

Treat this as a moderate-priority integrity risk. It is not listed as known exploited, but patching is appropriate where the software is deployed and reachable by users.

Technical view

The source identifies an unknown affected function in pyambic-pentameter and classifies the flaw as CSRF, with CVSS 3.1 score 4.3: AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. A patch commit is named, but affected versions and detailed vulnerable code paths are not provided.

Likely exposure

Exposure is limited to organizations running katlings pyambic-pentameter, especially if reachable by users through a browser. The source bundle does not identify affected versions, package identifiers, CPEs, or specific routes, so inventory confirmation is required.

Exploitation context

The CVSS vector indicates remote exploitation with low attack complexity and no attacker privileges, but user interaction is required. The bundle states KEV is false and provides no cited evidence of active exploitation.

Researcher notes

The public record is sparse: affected versions are listed as n/a, the vulnerable function is unknown, and only a commit hash is provided as the patch reference. Avoid broad product assumptions beyond pyambic-pentameter.

Mitigation direction

  • Apply upstream patch commit 974f21aa1b2527ef39c8afe1a5060548217deca8.
  • Check the project repository for fixed release or upgrade guidance.
  • Prioritize patching internet-facing or user-accessible deployments.
  • Document any compensating controls if patching is delayed.

Validation and detection

  • Inventory systems for katlings pyambic-pentameter usage.
  • Confirm deployed code includes the named patch commit.
  • Review exposed state-changing functionality for CSRF protection.
  • Record affected-version uncertainty in the vulnerability ticket.
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.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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
cve · low confidence lookup

CVE-2021-4275 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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
3Source 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2021-4275Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Products and packages named in the record

VendorProductVersion / packageStatus
katlingspyambic-pentametern/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.