Sensitive data disclosure via authenticated SSRF
Published Apr 17, 2025 · Updated Apr 18, 2025
Server-side request forgery in a-blogcms 3.1.15 allows remote authenticated users to read sensitive data through an entry-edit request. Public records identify /bid/1/admin/entry-edit/ as the affected route but do not disclose the destination parameter or the faulty validation operation. A low-privileged account is required, and the documented consequence is sensitive-data disclosure; the data source and broader effects remain undisclosed.
Summary
What happened
Server-side request forgery in a-blogcms 3.1.15 allows remote authenticated users to read sensitive data through an entry-edit request. Public records identify /bid/1/admin/entry-edit/ as the affected route but do not disclose the destination parameter or the faulty validation operation. A low-privileged account is required, and the documented consequence is sensitive-data disclosure; the data source and broader effects remain undisclosed.
The record
- CVE
- CVE-2025-29461
- Published
- Apr 17, 2025
- Updated
- Apr 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-918, CAPEC-664
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 17, 2025CVE publishedPublication date reported by the CVE source.
- Apr 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- morysummer Yuque exploit referenceproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo