<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 21 Oct 2026 23:17:30 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-113710</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-113710</link>
      <description>&lt;p&gt;ApostropheCMS is an open-source Node.js content management system. Prior to 4.33.0, the self-service password-change endpoint verifies the current password but does not use the login module’s failed-attempt counter, throttle, delay, or lockout mechanism. An attacker with a valid authenticated session can submit repeated guesses for the current password without receiving a lockout or throttle response. This issue is fixed in version 4.33.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ApostropheCMS is an open-source Node.js content management system. Prior to 4.33.0, the self-service password-change endpoint verifies the current password but does not use the login module’s failed-attempt counter, throttle, delay, or lockout mechanism. An attacker with a valid authenticated session can submit repeated guesses for the current password without receiving a lockout or throttle response. This issue is fixed in version 4.33.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-113710</guid>
    </item>
    <item>
      <title>GHSA-653j-g8j7-gh54 — ApostropheCMS: No Attempt Throttling on Authenticated Password-Change Endpoint Enables Unlimited Current-Password Guess…</title>
      <link>https://db.gcve.eu/vuln/ghsa-653j-g8j7-gh54</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: apostrophe&lt;/p&gt;
&lt;p&gt;**Summary**
The self-service password-change endpoint verifies the current password but does not use the login module’s failed-attempt counter, throttle, delay, or lockout mechanism. An attacker with a valid authenticated session can submit repeated guesses for the current password without receiving a lockout or throttle response.&lt;/p&gt;
&lt;p&gt;**Exact source path**
packages/apostrophe/modules/@apostrophecms/settings/index.js:621-664&lt;/p&gt;
&lt;p&gt;**The password-change route is:**
PATCH /api/v1/@apostrophecms/settings/password&lt;/p&gt;
&lt;p&gt;**The route calls the password verifier directly through:**
await self.handleProtectedSubform(req, subform, req.body );&lt;/p&gt;
&lt;p&gt;**The password verification path is:**
packages/apostrophe/modules/@apostrophecms/settings/index.js:514-542&lt;/p&gt;
&lt;p&gt;**async handlePasswordProtectedSubform(req, subform, payload) {
  try {
    await self.apos.user.verifyPassword(req.user, payload.passwordCurrent);
  } catch (e) {
    throw self.apos.error(
      &amp;#39;forbidden&amp;#39;,
      &amp;#39;apostrophe:passwordCurrentError&amp;#39;,
      { path: &amp;#39;passwordCurrent&amp;#39; }
    );
  }
  return subform;
}**&lt;/p&gt;
&lt;p&gt;**The verifier itself does not increment the login-attempt cache or enforce a delay:**
packages/apostrophe/modules/@apostrophecms/user/index.js:412-487&lt;/p&gt;
&lt;p&gt;**By contrast, the login route explicitly calls checkLoginAttempts and addLoginAttempt in:**
packages/apostrophe/modules/@apostrophecms/login/index.js:831-929&lt;/p&gt;
&lt;p&gt;**Local PoC**
The test used a disposable authenticated guest session against:&lt;/p&gt;
&lt;p&gt;Request:&lt;/p&gt;
&lt;p&gt;```
PATCH /api/v1/@apostrophecms/setting…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: apostrophe&lt;/p&gt;
&lt;p&gt;**Summary**
The self-service password-change endpoint verifies the current password but does not use the login module’s failed-attempt counter, throttle, delay, or lockout mechanism. An attacker with a valid authenticated session can submit repeated guesses for the current password without receiving a lockout or throttle response.&lt;/p&gt;
&lt;p&gt;**Exact source path**
packages/apostrophe/modules/@apostrophecms/settings/index.js:621-664&lt;/p&gt;
&lt;p&gt;**The password-change route is:**
PATCH /api/v1/@apostrophecms/settings/password&lt;/p&gt;
&lt;p&gt;**The route calls the password verifier directly through:**
await self.handleProtectedSubform(req, subform, req.body );&lt;/p&gt;
&lt;p&gt;**The password verification path is:**
packages/apostrophe/modules/@apostrophecms/settings/index.js:514-542&lt;/p&gt;
&lt;p&gt;**async handlePasswordProtectedSubform(req, subform, payload) {
  try {
    await self.apos.user.verifyPassword(req.user, payload.passwordCurrent);
  } catch (e) {
    throw self.apos.error(
      &amp;#39;forbidden&amp;#39;,
      &amp;#39;apostrophe:passwordCurrentError&amp;#39;,
      { path: &amp;#39;passwordCurrent&amp;#39; }
    );
  }
  return subform;
}**&lt;/p&gt;
&lt;p&gt;**The verifier itself does not increment the login-attempt cache or enforce a delay:**
packages/apostrophe/modules/@apostrophecms/user/index.js:412-487&lt;/p&gt;
&lt;p&gt;**By contrast, the login route explicitly calls checkLoginAttempts and addLoginAttempt in:**
packages/apostrophe/modules/@apostrophecms/login/index.js:831-929&lt;/p&gt;
&lt;p&gt;**Local PoC**
The test used a disposable authenticated guest session against:&lt;/p&gt;
&lt;p&gt;Request:&lt;/p&gt;
&lt;p&gt;```
PATCH /api/v1/@apostrophecms/setting…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-653j-g8j7-gh54</guid>
    </item>
  </channel>
</rss>
